-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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
r/aws_elasticsearchdomain: add support for saml_options #16424
Conversation
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.
Welcome @philof 👋
It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTING guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.
Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.
Thanks again, and welcome to the community! 😃
When will this be merged? |
bump |
Did you consider making the SAML options be there own resource so that it could be combined with the Okta terraform provider https://registry.terraform.io/providers/oktadeveloper/okta/latest/docs/resources/app_saml Elasticsearch -> Okta -> Elasticsearch SAML This would also solve the issue that the SAML config cannot be specified until after the domain is created. |
I have a new custom resource for aws_elasticsearch_domain_saml_options. Would you like a new pull request or to edit this one? |
I would probably create a new pull request. The separate resource should be perfect. |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Community Note
Fixes #16259
Release note for CHANGELOG:
Output from acceptance testing:
The overall structure is ready, but I still have an issue with
You cannot specify SAML options during domain creation
. The second apply in the create test results in a non-empty plan. I couldn't find another resource in the repo which restricts parameters on creation. I would greatly appreciate any guidance for this two-step creation process.