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
In current implementation, a data center's Id() is the data center's .DataCenterID.
However, in Akamai, a DC DataCenterID is not universally unique across a GTM domain; it is unique only within a GTM domain. Therefore, it may be worth considering making the Terraform data center resource's Id() something unique and domain-namespaced such as ${gtm_property}:${.DataCenterID} to avoid resource collision across properties.
For example, consider the following:
User creates a .tf creating a DC in some-domain
User executes terraform plan && terraform apply, in effect creating DC 123 in some-domain
User edits the .tf to target some-other-domain
Given the tfstate from step 2, Terraform may modify a DC 123 rather than create a fresh DC in the event that a DC 123 already exists in some-other-domain.
The text was updated successfully, but these errors were encountered:
In current implementation, a data center's
Id()
is the data center's.DataCenterID
.However, in Akamai, a DC
DataCenterID
is not universally unique across a GTM domain; it is unique only within a GTM domain. Therefore, it may be worth considering making the Terraform data center resource'sId()
something unique and domain-namespaced such as${gtm_property}:${.DataCenterID}
to avoid resource collision across properties.For example, consider the following:
.tf
creating a DC insome-domain
terraform plan && terraform apply
, in effect creating DC123
insome-domain
.tf
to targetsome-other-domain
tfstate
from step 2, Terraform may modify a DC123
rather than create a fresh DC in the event that a DC123
already exists insome-other-domain
.The text was updated successfully, but these errors were encountered: