Skip to content
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

Backport of test(e2e): Add module for iam user with credential rotation support into release/0.16.x #4725

Conversation

hc-github-team-secure-boundary
Copy link
Collaborator

Backport

This PR is auto-generated from #4718 to be assessed for backporting due to the inclusion of the label backport/0.16.x.

The below text is copied from the body of the original PR.


This PR updates an enos module that creates an IAM user to add support for credential rotation. The module was updated with the following

  • a new variable to the module to decide whether or not credential rotation support is needed (default: false)
  • if credential rotation support is enabled, the IAM user needs the force_destroy option set to true in order for terraform to successfully clean up afterwards (otherwise you'll get an error like Cannot delete entity, must delete access keys first. since new access keys were created)
  • if credential rotation is enabled, another policy is added to the user that allows the user to rotate its access keys

There will be a follow-up PR in boundary-enterprise to add the associated tests.
There will also be follow-up work to add similar tests using MinIO

@hc-github-team-secure-boundary hc-github-team-secure-boundary force-pushed the backport/moduli-e2e-credential-rotation/initially-renewing-macaw branch from 0aabeb2 to 9e54a35 Compare April 25, 2024 16:00
@hc-github-team-secure-boundary hc-github-team-secure-boundary merged commit b5f6704 into release/0.16.x Apr 25, 2024
@hc-github-team-secure-boundary hc-github-team-secure-boundary deleted the backport/moduli-e2e-credential-rotation/initially-renewing-macaw branch April 25, 2024 16:00
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.

2 participants