Support for ANY_USER_ACCOUNT in module vpc-sc egress rule. #1966
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 enables to support keyword ANY_USER_ACCOUNT when crafting VPC SC egress rule.
This keyword (identity_type) is currently not enabled by validation block in modules/vpc-sc/variable.tf.
Despite the fact that this option is specifically not enabled by fast vpc-sc module, it is indeed fully supported by underlying terraform resource google_access_context_manager_service_perimeters.
Desired state:
I applicable, I acknowledge that I have:
[ x] Read the contributing guide
[ x] Ran terraform fmt on all modified files
[ x] Regenerated the relevant README.md files using tools/tfdoc.py
[ x] Made sure all relevant tests pass