use for_each over count for iteration #96
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jurgenweber
changed the title
|
I am not on top of all of your processes, but this will be a breaking change because as per the issue you will trigger the AWS API problems. Maybe we want a migration process? Maybe some moves? Let me know. |
|
Hi @jurgenweber thanks for your contribution. Have you tested this code? It seems to have some invalid syntax. |
|
indeed, sorted now. Plans for me:
:) |
|
Any reason this has been put on ice? What do you need from me to get it over the line? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
what
moving to for_each for resources over count
why
I lost the ability to update an endpoint for 12 hours because of this. Standard terraform count vs for_each reasons (index changes with count).
references
#30