Enable usage of previously backed up settings when starting new ACA container #871
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.
An environment variable can be given to the container that will cause the startup scripts to use backup settings rather than generate new ones on container launch.
Mount the settings to a location within the container and give the environment variable HIRS_USE_IMPORTED_ETC_HIRS the path to the mountpoint within the container to look for those settings.
If the container doesn't already have settings defined, it will ingest the files under that mountpoint- copy them to the default settings folder and reset permissions necessary for container services to read them.
The files on the host will not be affected.
Example usage from a linux ACA: