Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reconsider how data center id is handled #4

Open
mdb opened this issue Jul 5, 2017 · 0 comments
Open

Reconsider how data center id is handled #4

mdb opened this issue Jul 5, 2017 · 0 comments

Comments

@mdb
Copy link
Collaborator

mdb commented Jul 5, 2017

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:

  1. User creates a .tf creating a DC in some-domain
  2. User executes terraform plan && terraform apply, in effect creating DC 123 in some-domain
  3. User edits the .tf to target some-other-domain
  4. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant