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

Defining parent-child relationships between teams (Teams & Sub-Teams) #207

Closed
jwlusby opened this issue Apr 15, 2020 · 5 comments
Closed

Comments

@jwlusby
Copy link

jwlusby commented Apr 15, 2020

This may not be an issue and may just be user error. Is there a way to define a parent-child relationship between teams?

As in this example where I have a team "Support Team" composed of two sub-teams "Sub-Team" A and "Sub-Team B"

Support Team
 |___Sub-Team A
 |___Sub-Team B

Terraform Version

Terraform v0.10.8

Affected Resource(s)

  • pagerduty_team
@stmcallister
Copy link
Contributor

This is currently supported by the PagerDuty API using the parent attribute on the team object, but not in the provider today.

@stmcallister
Copy link
Contributor

Just an update on this issue. It appears there is a bug in the teams API that isn't allowing the creation of parent relationships. Will keep this thread updated as I learn more.

@drastawi
Copy link
Contributor

Hey @stmcallister @jwlusby I just asked the PagerDuty folks and they confirmed the sub team/parent functionality is fully fixed now. I tested manually and it seems to work fine for me.

@stmcallister
Copy link
Contributor

Hi @drastawi, I'm still experiencing the same issues as before. When making a POST request to /teams and including the parent object, the parent object does not get created. I've put a request in to the team responsible for the /teams endpoint to address this issue. As mentioned, I'll keep you all posted on any updates.

@stmcallister
Copy link
Contributor

This feature was added with v1.9.6 of the provider. Going to close the issue. Please repost if you have further questions.

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

3 participants