Update GCP-VPC-Flow-logs-for-the-subnet-is-set-to-Off.json #117
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.
Per KeyBank:
Justification:
Google documentation states that flow logging is not supported for GLOBAL_MANAGED_PROXY also.
Per Google documentation (Terraform Registry ):
Flow logging isn't supported if the subnet purpose field is set to subnetwork is REGIONAL_MANAGED_PROXY or GLOBAL_MANAGED_PROXY
Note that INTERNAL_LOAD_BALANCER is fine to keep in the RQL for backward compatibility, but it is no longer a valid value and was changed to REGIONAL_MANAGED_PROXY. See https://cloud.google.com/load-balancing/docs/proxy-only-subnets#migrate-purpose
Description
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate)
Types of changes
Checklist