Add support for service account IAM variables to pf #2130
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR extends the project factory so that its fundamental design principle -- that the pf mostly wraps modules and exposes their full interface -- is also true for service accounts.
The practical use cases for this change are several, for example:
compute/networkUser
role on shared VPC hosts to GCE service accountsThe project factory interface for service accounts still supports as its default use case assigning roles to the project defined in YAML where the service accounts is created, with a slight change in names: where before we used
iam_project_roles
to specify the list of roles for the current project, we now useiam_self_roles
as the previous name clashes with the underlying service account module's interface.The new interface looks like this: