Allow custom source directories for testing #276
Draft
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.
At the moment, testing versions/release notes is hard for folks without the source files (e.g QA/FE teams).
This supports passing in a custom directory via env variables to the compiled binary. Custom version metadata and release notes can then be stored in the custom directory.
It is intended for docker containers where we can simply run:
docker run ... -e DEV_METADATA_DIR=/tmp/metadata