Skip to content

Use a map for root_block_device instead of list #425

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

Open
Yethal opened this issue Mar 31, 2025 · 4 comments
Open

Use a map for root_block_device instead of list #425

Yethal opened this issue Mar 31, 2025 · 4 comments

Comments

@Yethal
Copy link

Yethal commented Mar 31, 2025

Is your request related to a new offering from AWS?

Is this functionality available in the AWS provider for Terraform? See CHANGELOG.md, too.

  • No 🛑: please wait to file a request until the functionality is avaialble in the AWS provider
  • Yes ✅: please list the AWS provider version which introduced this functionality

Is your request related to a problem? Please describe.

Instead of using a list of maps for root_block_device I'd like a map to be used. There can't be more than one root_block_device anyway and turning it into a single map will make it easier for terraform wrappers to merge in configuration
As suggested in #396, I'm opening an issue instead of keeping PR open.

Describe the solution you'd like.

Describe alternatives you've considered.

Additional context

Copy link

github-actions bot commented May 1, 2025

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label May 1, 2025
@Yethal
Copy link
Author

Yethal commented May 5, 2025

unstale

@github-actions github-actions bot removed the stale label May 6, 2025
Copy link

github-actions bot commented Jun 5, 2025

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jun 5, 2025
@Yethal
Copy link
Author

Yethal commented Jun 6, 2025

unstale

@github-actions github-actions bot removed the stale label Jun 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants