[Feature][Core] Override env parameters via command line arguments

[liugddx]

Search before asking

• [X] I had searched in the feature and found no similar feature requirement.

Description

Override env parameters via command line arguments

Usage Scenario

No response

Related issues

No response

Are you willing to submit a PR?

• [X] Yes I am willing to submit a PR!

Code of Conduct

• [X] I agree to follow this project's Code of Conduct

[liugddx]

Do we now use command line parameters to directly replace the parameters in config or use placeholder replacement in config?

1. direct replacement start-seatunnel-flink-connector-v2.sh -c config.conf -i job.name=test

env {
job.name = seatunnel
}

2. placeholder replacement

start-seatunnel-flink-connector-v2.sh -c config.conf -i jobName=test

env {
job.name = ${jobName}
}

[liugddx]

Do we now use command line parameters to directly replace the parameters in config or use placeholder replacement in config?

1. direct replacement start-seatunnel-flink-connector-v2.sh -c config.conf -i job.name=test

env {
job.name = seatunnel
}

2. placeholder replacement

start-seatunnel-flink-connector-v2.sh -c config.conf -i jobName=test

env {
job.name = ${jobName}
}

The second method is now supported, but sometimes the placeholder will not be configured

[liugddx]

Do we now use command line parameters to directly replace the parameters in config or use placeholder replacement in config?

1. direct replacement start-seatunnel-flink-connector-v2.sh -c config.conf -i job.name=test

env {
job.name = seatunnel
}

2. placeholder replacement

start-seatunnel-flink-connector-v2.sh -c config.conf -i jobName=test

env {
job.name = ${jobName}
}

The second method is now supported, but sometimes the placeholder will not be configured

@Hisoka-X @EricJoy2048 @TyrantLucifer Any suggestions?

[Hisoka-X]

I think method 1 can only support replace parameter in env. But not use -i, use -p or other. Method 2 is good for replace the placeholder.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity for 30 days. It will be closed in next 7 days if no further activity occurs.

[github-actions[bot]]

This issue has been closed because it has not received response for too long time. You could reopen it if you encountered similar problems in the future.