kovagoadi/hunfabric
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Cosmetic and linter fixes (#3981)

Browse Source
This commit is contained in:
Simone Ruffilli
2026-05-22 10:28:01 +02:00
committed by GitHub
parent 87ede610c4
commit 1594a01c6f
11 changed files with 9 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
modules/artifact-registry/README.md
View File

@@ -419,4 +419,3 @@ module "legacy_custom_repo" {
}
# tftest modules=1 resources=1 inventory=legacy-custom.yaml
```

2
modules/data-catalog-policy-tag/schemas/policy-tag.schema.json
View File

@@ -150,4 +150,4 @@
}
}
}
}
}

4
modules/folder/README.md
View File

@@ -729,11 +729,11 @@ module "folder" {
## IAM Deny Policies
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions within the folder and all of its descendants, regardless of the roles they have been granted.
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions within the folder and all of its descendants, regardless of the roles they have been granted.
You can define Deny policies using the `iam_deny_policies` variable. Each policy requires you to specify the principals and permissions to deny. You can optionally define exception principals, exception permissions, and conditions to tailor the restriction.
Note that IAM Deny policies require a specific prefix for principal definitions (e.g., `principalSet://goog/public:all` or `principalSet://goog/group/group-email@example.com`), and permissions must be prefixed with the service fully qualified domain name (e.g., `iam.googleapis.com/serviceAccountKeys.create`).
Note that IAM Deny policies require a specific prefix for principal definitions (e.g., `principalSet://goog/public:all` or `principalSet://goog/group/group-email@example.com`), and permissions must be prefixed with the service fully qualified domain name (e.g., `iam.googleapis.com/serviceAccountKeys.create`).
```hcl
module "folder" {

2
modules/organization/README.md
View File

@@ -1013,7 +1013,7 @@ module "org" {
## IAM Deny Policies
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions, regardless of the roles they have been granted.
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions, regardless of the roles they have been granted.
You can define Deny policies using the `iam_deny_policies` variable. Each policy requires you to specify the principals and permissions to deny, and optionally allows you to define exception principals, exception permissions, and conditions.

2
modules/project-factory/schemas/taxonomy.schema.json
View File

@@ -150,4 +150,4 @@
}
}
}
}
}

2
modules/project/README.md
View File

@@ -2248,7 +2248,7 @@ module "project" {
## IAM Deny Policies
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions within the project, regardless of the roles they have been granted.
[IAM Deny policies](https://cloud.google.com/iam/docs/deny-overview) allow you to set centralized guardrails that prevent principals from using specific permissions within the project, regardless of the roles they have been granted.
You can define Deny policies using the `iam_deny_policies` variable. Each policy requires you to specify the principals and permissions to deny. You can optionally define exception principals, exception permissions, and conditions to tailor the restriction.