-
Notifications
You must be signed in to change notification settings - Fork 930
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation issue in 01-resman/teams ? #673
Comments
The example in the README is correct, but you need to use it in a Just put something like this in your team_folders = {
test = {
descriptive_name = "foo@example.org"
group_iam = {
"foo@example.org" = ["roles/viewer"]
}
impersonation_groups = ["foo@example.org"]
}
} |
Thanks for the clarification. Keep up the good work! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just wondering if there are some small adjustments need to be made on Readme.md and variables.tf.
Just my setup?
Readme Customization example:
team_folders = {
team-a = {
descriptive_name = "Team A"
group_iam = {
"team-a@gcp-pso-italy.net" = [
"roles/viewer"
]
}
impersonation_groups = ["team-a-admins@gcp-pso-italy.net"]
}
}
Adding that directly to variables.tf (instead of the example already present there) will only give you error: An argument named "team_folders" is not expected here.
To follow example already present in variables.tf (commented out) it should be this:
variable "team_folders" {
default = {
team-a = {
descriptive_name = "Team A"
group_iam = {
"team-a-group@example.com" = ["roles/owner", "roles/resourcemanager.projectCreator"]
}
impersonation_groups = ["team-a-admins@example.com"]
}
}
}
(ok, there is different roles). Perhaps the IAM group names should be in sync what is in the example? Not to take away credits to the gcp-pso-italy.net team...
Also just remove the comments in variables.tf for team_folders will give you an error. The "team-a-group@example.com" needs to be in quotes to get it working.
Or is it just my setup that is causing this?
The text was updated successfully, but these errors were encountered: