[opt](cloud) Support multiple config files in start.sh#63924
Open
gavinchou wants to merge 1 commit into
Open
Conversation
Contributor
|
Thank you for your contribution to Apache Doris. Please clearly describe your PR:
|
Contributor
Author
|
run buildall |
Contributor
Author
|
/review |
Contributor
|
OpenCode automated review failed and did not complete. Error: Error: Token refresh failed: 401 Please inspect the workflow logs and rerun the review after the underlying issue is resolved. |
Contributor
Author
|
/review |
Contributor
|
OpenCode automated review failed and did not complete. Error: Error: Token refresh failed: 401 Please inspect the workflow logs and rerun the review after the underlying issue is resolved. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What problem does this PR solve?
Support loading cloud start environment variables from multiple config files without forcing deployments to rely on
process_nameas the only config file name.This keeps the default behavior of loading
${process_name}.conf, and adds support forCONF_FILESwith comma-separated or whitespace-separated entries, glob patterns, and absolute paths. Config files are loaded in order, later files can override earlier files, while variables already set before config loading keep priority.Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
cloud/script/start.shpreviously loaded only${process_name}.conf, which made multi-instance or layered config deployments harder to express.Release note
Support specifying multiple cloud config files through
CONF_FILESincloud/script/start.sh.Check List (For Author)
${process_name}.confloading.CONF_FILESlists.bash -n cloud/script/start.sh.cloud/script/start.shcan now load multiple config files throughCONF_FILES.