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

backend/s3: Move assume role parameters to block #30495

Closed
Tracked by #33687
gdavison opened this issue Feb 8, 2022 · 2 comments · Fixed by #33630
Closed
Tracked by #33687

backend/s3: Move assume role parameters to block #30495

gdavison opened this issue Feb 8, 2022 · 2 comments · Fixed by #33630
Labels
backend/s3 enhancement new new issue not yet triaged

Comments

@gdavison
Copy link
Contributor

gdavison commented Feb 8, 2022

The assume role parameters are currently at the root level.

  1. Add block assume_role with
  • duration of type duration
  • external_id
  • policy
  • policy_arns
  • role_arn (required)
  • session_name
  • tags
  • transitive_tag_keys
  1. Deprecate
  • role_arn
  • session_name
  • external_id
  • assume_role_duration_seconds
  • assume_role_policy
  • assume_role_policy_arns
  • assume_role_tags
  • assume_role_transitive_tag_keys
@gdavison gdavison added enhancement new new issue not yet triaged backend/s3 labels Feb 8, 2022
@blowfishpro
Copy link

It seems like this will break the ability to set these variables via CLI arguments (e.g. -backend-config=role_arn=...) or via environment variables (e.g. TF_CLI_ARGS_init='-backend-config=role_arn=...'). Before this is removed entirely is there any chance #21830 could be addressed so that block variables can be set via -backend-config, or that specific environment variables could be added for these? (or #13022 addressed but I assume that's a much deeper change within terraform)

Copy link
Contributor

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend/s3 enhancement new new issue not yet triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants