Update validation check for IAMAlias on vault_aws_auth_backend_config_identity resource #2536
+58
−10
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.
Description
Update validation logic for IAMAlias parameter on
vault_aws_auth_backend_config_identity
resource. Vault added support forcanonical_arn
in Vault 1.16 but the Vault provider has a validation check that only allowsrole_id
,unique_id
, andfull_arn
.This change:
canonical_arn
to be specified as a valid value for IAMAlias onvault_aws_auth_backend_config_identity
resourcevault_aws_auth_backend_config_identity
resourceChecklist
Output from acceptance testing:
Community Note
PCI review checklist
I have documented a clear reason for, and description of, the change I am making.
If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
If applicable, I've documented the impact of any changes to security controls.
Examples of changes to security controls include using new access control methods, adding or removing logging pipelines, etc.