gavinchou opened a new pull request, #63924:
URL: https://github.com/apache/doris/pull/63924
### What problem does this PR solve?
Support loading cloud start environment variables from multiple config files
without forcing deployments to rely on `process_name` as the only config file
name.
This keeps the default behavior of loading `${process_name}.conf`, and adds
support for `CONF_FILES` with 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.sh` previously 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_FILES` in
`cloud/script/start.sh`.
### Check List (For Author)
- Test: Manual test
- Verified default `${process_name}.conf` loading.
- Verified comma-separated and whitespace-separated `CONF_FILES` lists.
- Verified glob pattern loading.
- Verified missing config files are skipped.
- Verified absolute config file paths.
- Verified pre-existing environment variables are not overridden by
config files.
- Ran `bash -n cloud/script/start.sh`.
- Behavior changed: Yes. `cloud/script/start.sh` can now load multiple
config files through `CONF_FILES`.
- Does this need documentation: No
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
