[26432] Enable late handling of cloud-init template rendering #7
Conversation
This file contains 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
This is the same issue referenced in the pull [request](Azure/terraform-azurerm-computegroup#20) The ip_configuration now requires a primary setting.
This is instead of using an already rendered file as input as I had issues where the config file I wanted to use didn't exist yet in this module.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR is an extension to another PR that has been open since Nov 2018 on the upstream repo: #5
(that PR is necessary if using the latest azurerm terraform provider, which we are)
This one enables late rendering of cloud-init template with vars (passed into the module as a map on key/value pairs) that get values late in the deployment process.