-
Notifications
You must be signed in to change notification settings - Fork 3
feat: add coderd_organization_group_sync
resource
#248
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
base: main
Are you sure you want to change the base?
Conversation
coderd_organization_group_sync_resource
coderd_organization_group_sync
resource
f7c7ea3
to
2fb0bd4
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looking at the code again, I'm remember the main motivation for making this a nested block: you can only have exactly one group sync config per organization. managing it by a resource instead means that you could theoretically specify multiple of them pointing at the same org, which would be a logic error and produce inconsistent behavior. :\
it's unfortunate that having it as a nested block doesn't work.
- `group_sync` (Block, Optional) Group sync settings to sync groups from an IdP. (see [below for nested schema](#nestedblock--group_sync)) | ||
- `group_sync` (Block, Optional, Deprecated) Group sync settings to sync groups from an IdP. | ||
|
||
~> **Deprecated** This block is deprecated. Use the `coderd_organization_group_sync` resource instead. (see [below for nested schema](#nestedblock--group_sync)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can the "see below" bit stay attached up above? this positioning feels weird
|
||
data "coderd_organization" "test_data" { | ||
id = coderd_organization.test.id | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
} | |
} | |
missing \n
Fixes #230.
To avoid users running into circular dependency issues with the
group_sync
block, we'll deprecate the block and add a resource solely for configuring organization group sync.