Skip to content

branch-4.1: [opt](cloud) Support multiple config files in start.sh #63924#65162

Merged
yiguolei merged 1 commit into
branch-4.1from
auto-pick-63924-branch-4.1
Jul 3, 2026
Merged

branch-4.1: [opt](cloud) Support multiple config files in start.sh #63924#65162
yiguolei merged 1 commit into
branch-4.1from
auto-pick-63924-branch-4.1

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

Cherry-picked from #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
@github-actions github-actions Bot requested a review from yiguolei as a code owner July 2, 2026 10:14
@hello-stephen

Copy link
Copy Markdown
Contributor

Thank you for your contribution to Apache Doris.
Don't know what should be done next? See How to process your PR.

Please clearly describe your PR:

  1. What problem was fixed (it's best to include specific error reporting information). How it was fixed.
  2. Which behaviors were modified. What was the previous behavior, what is it now, why was it modified, and what possible impacts might there be.
  3. What features were added. Why was this function added?
  4. Which code was refactored and why was this part of the code refactored?
  5. Which functions were optimized and what is the difference before and after the optimization?

@hello-stephen

Copy link
Copy Markdown
Contributor

run buildall

@yiguolei

yiguolei commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

skip buildall

@yiguolei yiguolei merged commit 7eddd98 into branch-4.1 Jul 3, 2026
31 of 33 checks passed
@morningman morningman deleted the auto-pick-63924-branch-4.1 branch July 8, 2026 14:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants