#6 Support services on admins/managers

@mikesir When creating a group using an ED Service (as Terraform does), ED will automatically make the ED Service an administrator of the group. If your TF config doesn't include the ED service as a service admin, you can lose your ability to manage the service using TF (at least with the service that created it).

We should probably ensure that the TF config includes the UUSID of the service being used to run Terraform.

How can we tell the UUSID of the service that TF is using to create the group?

Where would we make that assertion?

Should we throw an error or just modify the config on the fly (like ED does)?

added 9 commits

• 88568ce5...efc0863e - 2 commits from branch devcom/terraform-providers:main
• 0a026d14 - support replication targets
• fe175286 - update naming
• 550efe61 - make replication_targets optional
• 9a788259 - update docs
• 73d5c3b2 - Merge remote-tracking branch 'upstream/main' into main
• 345cf564 - resolve merge conflict
• 0c476420 - update docs

Compare with previous version

resolved all threads

added 1 commit

• 2658fe26 - set replication targets when a group is created (not just on update)

Compare with previous version

added 6 commits

• 2658fe26...286f7f23 - 2 commits from branch devcom/terraform-providers:main
• 1eb7d5c5 - Merge remote-tracking branch 'upstream/main' into main
• 67610ca0 - Merge branch 'main' into service-managers-admins
• d3a4459c - Make sure the TF provider service account is a service admin
• 1e0ae32c - ignore vim backups

Compare with previous version

marked this merge request as ready

assigned to @mikesir

LGTM. Nice work!

merged

mentioned in commit f067a456

approved this merge request