Use terraform to maintain the organizational structure #14
Commits on Jul 15, 2024
Commits on Jul 16, 2024
Commits on Jul 20, 2024
Commits on Jul 24, 2024
-
The wiki seems like a possibility and the security alerts seems like a good thing to enable by default until someone complains.
-
Comment the main terraform file with descriptions of what each sectio…
…n does. Removes the security template and other sections that aren't 100% obviously critical. We can always re-add these later, but teams can also configure this manually.
-
Use domain specific naming for variables.
This should make it easier to determine what a parent team relates to versus what a child team relates to.
-
Re-add review request delegation.
I didn't see it was used for the playground repo.
-
-
-
-
-
The teams are maps, not lists.
These need to be merged rather than concatenated.
-
Revert change, use dynamic members.
Adds a comment to hopefully reduce confusion.
-
Remove maintainers collections where they are unnecessary.
The Django Commons admin team will have access to all teams by being owners in the organization. That isn't controlled by the terraform plan.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.