You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
3-networks-hub-and-spoke - terraform re apply causes hierarchical firewall policy rule display name collision - either delete or rename attribute - not idempotent
#380
Closed
obriensystems opened this issue
Apr 13, 2024
· 3 comments
This is why the clause is stated "only once" because it is not idem potent
"You must manually plan and apply the shared environment (only once) since the development, non-production and production environments depend on it."
obriensystems
changed the title
3-networks-hub-and-spoke - terraform re apply causes firewall rule display name collision - either delete or rename attribute
3-networks-hub-and-spoke - terraform re apply causes hierarchical firewall policy rule display name collision - either delete or rename attribute - not idempotent
Apr 13, 2024
After #379
This is why the clause is stated "only once" because it is not idem potent
"You must manually plan and apply the shared environment (only once) since the development, non-production and production environments depend on it."
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/gh360-day0-deploy-example/3-networks-hub-and-spoke/README.md
https://github.com/GoogleCloudPlatform/pbmm-on-gcp-onboarding/blob/main/3-networks-hub-and-spoke/envs/shared/hierarchical_firewall.tf#L21
The text was updated successfully, but these errors were encountered: