Better support for "foreach" using sets or lists#224
Open
Kolky wants to merge 2 commits intocycloidio:masterfrom
Open
Better support for "foreach" using sets or lists#224Kolky wants to merge 2 commits intocycloidio:masterfrom
Kolky wants to merge 2 commits intocycloidio:masterfrom
Conversation
added 2 commits
March 28, 2023 14:52
…ded more azurem nodes.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When using "foreach" in your terraform a lot of nodes end up missing in the generated graph. I adapted the
state.gogenerator to detect instances of resources either by their index or by their name (if using maps/sets). I post fix the name of a resource with ! and then either the index or name of the resource.This PR also includes additional azure nodes, because it mostly contained network related things and is missing some common other nodes.
Example:
