we’re trying out teams, created a team and added people to it. We also associated an escalation policy with the team (to be able to list services and the corresponding team who is owning that service).
Let’s say we have a DevOps team:
The escalation policy is as follows:
- Notify either Alice or Bob, depending on their shifts
- Escalate to the DevOps team.
- Escalate to the CTO, Carl.
When we associate that escalation policy to a service, Carl gets auto-added to the DevOps team. This is unexpected because we don’t want to add Carl to the team. If we did that, Carl would be on all teams because ultimately, he is the last step in each escalation policy. This applies not only to Carl but to anyone who is part of multiple escalation policies.
As this behavior is well-documented, it seems to be intentional. We only noticed this thanks to Terraform – associating the team with an escalation policy created an unexpected diff on Carl.
What’s the thinking behind this? Any suggestions to avoid adding Carl to 20 teams?