feat: allow .tfvars to be structured in subfolders #340
+1
−1
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
Especially on level 4 landing zone developers can now structure their tfvars files into sub folders (e.g. networking, compute). The rover CLI interface stays the same.
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.
With this change caf developers (especially on level 4) can structure their tfvars files into sub folders (networking, compute etc.). When running rover providing the
-var-folderparameter now the provided folder and all subfolders will be searched for .tfvars files and used when running rover.The rover CLI interface stays the same.
This change might break things when existing caf project structures have folders including tfvars next to tfvars files. As far as I can see this is not the case for asvm related projects.