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
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.
The text was updated successfully, but these errors were encountered:
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.
When terraform apply happens (and this tutorial has previously been run or the tenant already has a team called
demo
):Impact is limited here because it relies on people re-running the demo - but it's not zero impact.
The text was updated successfully, but these errors were encountered: