Add allowed_email_sans field to write and update functions of vault_cert_auth_backend_role #1140
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#282 introduced many missing optional parameters in vault_cert_auth_backend_role, but missed validating and reading the
allowed_email_sans
field in thecertAuthResourceUpdate
andcertAuthResourceWrite
functions. Terraform currently correctly reads and plans for updatingallowed_email_sans
, but never actually does it.For example, locally I have defined a set of emails that are added to the
allowed_common_names
parameter andallowed_email_sans
. Onlyallowed_common_names
is created/updated.allowed_email_sans
is not.Community Note
Release note for CHANGELOG:
Output from acceptance testing: