chore: introduce .env.override for docker-compose #1584
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.
Changes
This PR adds the
.env.override
file that will be used together with the.env
file to populate environment variables used withdocker compose
. The purpose of this file is to ease the maintenance of forked repositories by allowing them to override environment variables and avoiding merge conflicts.Related issue: #1405
For example, we could simply duplicate the collector env var into our
.env.override
to use our distribution:Merge Requirements
For new features contributions please make sure you have completed the following
essential items:
* [ ]CHANGELOG.md
updated to document new feature additions* [ ] Appropriate documentation updates in the docs* [ ] Appropriate Helm chart updates in the helm-chartsMaintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.