docker: add profile support and improved endpoint access. #5323
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.
Summary
Final feature from #5197
These changes make the docker container easier to use without providing a
config.json
file, and make the behavior more expected when aconfig.json
file is provided.config.json
file via/etc/algorand/config.json
or thePROFILE
environment variable would be likely to miss this option and be unable to access the REST API.PROFILE
environment variable. When set algocfg is used to initialize theconfig.json
file.Test Plan
Manual testing. By mounting a data directory in different scenarios observe that the config.json file is set as expected.
EndpointAddress Override
Mount a config.json file
Observe that the EndpointAddress is added to the other settings:
algocfg profile
Add a PROFILE environment variable
Observe that the profile settings, and EndpointAddress setting are properly set: