-
Notifications
You must be signed in to change notification settings - Fork 207
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
Wrong definition of email_domain_id in brand resource #1855
Comments
This was changed from argument to attribute for the The way this should be done is:
|
I recognised that there was a change #1824 but how could the email_domain_id attached to brand if you have multiple brands as okta_email_domain only support one brand_id? ` resource "okta_email_domain" "example" { |
@mvitt Thanks for clarification. How I can assign multiple brand_id's to the same okta_email_domain? |
There is only one brand id per email_domain https://developer.okta.com/docs/api/openapi/okta-management/management/tag/EmailDomain/#tag/EmailDomain/operation/createEmailDomain |
@duytiennguyen-okta thanks for pointing me to API with only one brand_id If you request the email domains one "emailDomainId" could be assigned to multiple brands. Ho to assign one email domain to multiple brands now? Until 4.6.1 https://registry.terraform.io/providers/okta/okta/4.6.1/docs/resources/brand this was possible by setting resource "okta_brand" "example1" { resource "okta_brand" "example2" { |
OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-690454 |
Are there any change planned? We still stuck on Okta TF plugin 4.4.3 until this issue is fixed. |
Community Note
Terraform Version
1.6.6
Affected Resource(s)
Terraform Configuration Files
Debug Output
Panic Output
Expected Behavior
terraform apply will change the "email_domain_id" for brand so it should not be defined as Read-Only
Can this be done in the Admin UI?
Can this be done in the actual API call?
Actual Behavior
Steps to Reproduce
terraform validate
Important Factoids
References
The text was updated successfully, but these errors were encountered: