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

Cannot be two teams with the same identifier #22

Open
agardnerIT opened this issue Oct 11, 2024 · 1 comment
Open

Cannot be two teams with the same identifier #22

agardnerIT opened this issue Oct 11, 2024 · 1 comment

Comments

@agardnerIT
Copy link
Collaborator

agardnerIT commented Oct 11, 2024

When terraform apply happens (and this tutorial has previously been run or the tenant already has a team called demo):

│ Error: There cannot be 2 teams with the same identifier.
│ 
│   with dynatrace_ownership_teams.demo,
│   on team.tf line 1, in resource "dynatrace_ownership_teams" "demo":
│    1: resource "dynatrace_ownership_teams" "demo" {

Impact is limited here because it relies on people re-running the demo - but it's not zero impact.

@KatharinaSick
Copy link
Contributor

We could solve this by running terraform import on the team before actually applying our configuration: https://developer.hashicorp.com/terraform/cli/commands/import

This would cause problems if the destroy script in one of the Codespaces is called though as the owner team of the Kubernetes workloads would then be gone. Still less impact as with the current situation. An alternative would be to add the Codespace name to the teams name & identifier but in that case we would also have to replace the dt.owner annotations in the deployment manifests which would lead to more noise in the generated PRs which is not really nice as well.

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

2 participants