Allow preventing creation of billing IAM roles in FAST, add instructions on delayed billing association #1207
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ludoo
changed the title
sruffilli
approved these changes
Mar 3, 2023
juliocc
approved these changes
Mar 3, 2023
lcaggio
pushed a commit
that referenced
this pull request
May 5, 2023
…ons on delayed billing association (#1207) * stage 0 * resman and networking stages * tfdoc * security stage
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 allows using FAST in situations where control of the billing account resides with a different entity.
It does so by implementing a switch that avoids the use of IAM bindings for billing, and showing a specific apply flow that allows pausing while billing associations are configured externally, and then resuming and completing the stage.