Allow nested attributes of input variables to be individually configured #1391
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.
Issue #, if available: #1286
Description of changes:
Currently, for each of the Terraform module's input variables, consumers must either configure all or none of that variable's nested attributes; it is not possible to only configure some of the nested attributes.
However, it is quite a common scenario to want to only configure some attributes, e.g. enabling a single optional dashboard or enabling a single optional source, without being concerned about any of the other attributes (i.e. needing to copy all the other default values).
This PR changes the definition of each of the nested attributes to be individually
optional(...)but without breaking the interface / contract with existing consumers.N.B. I can see that PR #1276 also introduces some changes to improve the usability of the module (in fact, we have made identical changes for our own deployment). Thankfully, my PR should not conflict with any changes in #1276.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.