Allow overriding config in config.*.yaml
using override_config: true
, fixes #4100, fixes #4079, fixes #4099
#4118
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.
The Problem/Issue/Bug:
DDEV v1.20.0 introduced the merging approach to
config.*.yaml
that most people seemed to expect over the years, but it turned out there were many people who had used the old (overwrite everything) behavior to good effect and needed the old behavior.How this PR Solves The Problem:
Add
override_config: true
option that can be added to anyconfig.*.yaml
file to signal that its contents should override instead of merging.Manual Testing Instructions:
Add
override_config: true
to anyconfig.*.yaml
and the behavior for that file only is changed to override instead of merge.Try out the things people complained about:
nfs_mount_enabled: false
additional_hostnames: []
Automated Testing Overview: