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

feat: set_aws_env_vars #184

Merged
merged 6 commits into from
Dec 5, 2023
Merged

feat: set_aws_env_vars #184

merged 6 commits into from
Dec 5, 2023

Conversation

brivu
Copy link
Contributor

@brivu brivu commented Dec 5, 2023

Currently, the assume_role_with_web_identity command generates temporary AWS keys that gets written to a temporary file, enabling users to create multiple profiles without having to alter BASH_ENV. This was helpful for users who ran workflows requiring multiple profiles to run their aws commands.

However, this change broke for many users (see #179) who were relying on the AWS key being written to BASH_ENV.

This pull request adds ads the set_aws_env_vars parameter to the assume_role_with_web_identity command that enables to write the keys to a temporary file when set to false. Otherwise, it automatically writes to BASH_ENV by default.

@brivu brivu force-pushed the feat/configure_aws_env_vars branch from 0aaf8f5 to 17d5b68 Compare December 5, 2023 09:52
@brivu brivu self-assigned this Dec 5, 2023
.circleci/test-deploy.yml Outdated Show resolved Hide resolved
@brivu brivu merged commit bcd8553 into master Dec 5, 2023
2 checks passed
@brivu brivu deleted the feat/configure_aws_env_vars branch December 5, 2023 21:04
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.

Broken AWS Credentials after #164 (4.1.2) multiple calls to setup don't use newest role
2 participants