Introduce proper backend config merge #61
Merged
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.
Motivation
Backend configs are currently merged selectively, due to this some options are not usable as the override file's takes precedent over the user defined backend options.
Note: users have to use the right
use_path_style
/force_path_style
option for the given provider, this is not handled by tflocal.Changes
test_s3_backend_configs_merge
, checks generated override file for the following extra options added by the "user":acl
encryption
use_path_style