[Enhancement]:

[prowlaiii]

Description

I often use a for_each statement as an "if" to conditionally deploy resources or modules based on feature flags or other options, but then each resource when its used needs to be presented as if it had an iterator eg. my_resource["yes"]. Would it be possible to implement an "if" operator instead, which would make the code more readable and also remove the pseudo iterator from calls to it (and also terraform output). Something like: deploy_if = <condition> rather than: for_each = <condition> ? {deploy="yes"} : {} or: count = <condition> ? 1 : 0

Affected Resource(s) and/or Data Source(s)

(none)

Potential Terraform Configuration

resource "xxxxxx" "my_blah" {
   deploy_if = var.options.i_want_my_blah
   .....
}

References

No response

Would you like to implement a fix?

None

[github-actions[bot]]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hey @prowlaiii 👋 Thank you for taking the time to raise this! For changes to how Terraform operates at its core, you'll want to open a feature request in the Terraform Core repository, rather than at the AWS provider level (this repository). With that in mind, I'm going to close this issue.

[github-actions[bot]]

[!WARNING] This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

[github-actions[bot]]

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.