fix: run dotenv-expand for each file separately #18981
Open
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.
Description
This PR makes the env resolution to match with docker-compose and bash, which was the reason of the breaking change of dotenv-expand v12 (motdotla/dotenv-expand#134 (comment)).
I tested the behavior of docker-compose with the following compose file.
The upside of this approach is that we will be aligned with other ecosystems.
The downside of this approach is that composing multiple env files will be difficult. For example,
means
which is not likely most people expects.
fixes #18975