Skip to content

Conversation

maxrabin
Copy link

Description

The API does not require updates to role_arns to force an update, only updates to name according to the docs: https://developer.hashicorp.com/vault/api-docs/secret/aws#create-update-role

Closes #2530

Checklist

  • Added CHANGELOG entry (only for user-facing changes)
  • Acceptance tests where run against all supported Vault Versions

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

Community Note

  • Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
  • Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

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.

…_role`

The API does not require updates to `role_arns` to force an update, only updates to `name` according to the docs: https://developer.hashicorp.com/vault/api-docs/secret/aws#create-update-role
@maxrabin maxrabin requested a review from a team as a code owner July 16, 2025 09:27
@maxrabin maxrabin requested a review from lane-wetmore July 16, 2025 09:27
Copy link

hashicorp-cla-app bot commented Jul 16, 2025

CLA assistant check
All committers have signed the CLA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Enhancement]: vault_aws_secret_backend_role "role_arns" should not be ForceNew = true
1 participant