-
Notifications
You must be signed in to change notification settings - Fork 139
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
feat(tls_activation): support mutual_authentication_id in domain activation at creation #875
feat(tls_activation): support mutual_authentication_id in domain activation at creation #875
Conversation
This adds a (failing) test-case for creating a domain activation with a mutual authentication configuration. Currently the test case fails because the check on the resource shows it does not match the state.
583ac5c
to
b6fd587
Compare
The mutual_authentication_id can only be set once an activation has already been created. This commit implements the Update call immediately after the Create call if the mutual_authentication_id is set in the resource configuration. It fixes the failing test case added in the previous commit.
b6fd587
to
d7de6a6
Compare
This looks good so far, I'll pull it down to my machine and run the acceptance tests. |
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.
Acceptance test passes.
Thank you for the contribution! |
Hey @kpfleming do you know when a new release will be available with this change? |
We haven't scheduled one yet, but if possible I'll get one made early next week. |
Version 5.12.0 was just released. |
This fails on
main
because themutual_authentication_id
is not set on an activation when it is createdbut it is set in the terraform state.
mutual_authentication_id
cannot be set when activation is createdUpdate
the domain activation once it has been created to add themutual_authentication_id
to the configuration.Related to /issues/870 and #873