yzeng1618 opened a new pull request, #17996:
URL: https://github.com/apache/dolphinscheduler/pull/17996

   <!--Thanks very much for contributing to Apache DolphinScheduler, we are 
happy that you want to help us improve DolphinScheduler! -->
   
   ## Purpose of the pull request
   
   <!--(For example: This pull request adds checkstyle plugin).-->
   Harden startup script validation and fix -i variable quoting issues for the 
SeaTunnel task to prevent path traversal and shell injection. Also update 
outdated SeaTunnel task documentation.
   ## Brief change log
   
   <!--*(for example:)*
   - *Add maven-checkstyle-plugin to root pom.xml*
   -->
   
   - Add startupScript allowlist validation in 
SeatunnelParameters#checkParameters
   
   - Add bash-safe quoting/escaping for -i variable values in SeatunnelTask
   
   - Support values containing single quotes ' in -i parameters
   
   Update SeaTunnel task docs (EN/ZH):  refresh links to 2.3.12
   ## Verify this pull request
   
   This pull request is already covered by existing tests, such as:
   - Unit tests in 
`dolphinscheduler-task-plugin/dolphinscheduler-task-seatunnel`: 
`org.apache.dolphinscheduler.plugin.task.seatunnel.SeatunnelTaskTest` (covers 
`buildOptions()` including config suffix detection, reading config from 
Resource Center, and `-i` parameter generation).
   
   ## Pull Request Notice
   [Pull Request 
Notice](https://github.com/apache/dolphinscheduler/blob/dev/docs/docs/en/contribute/join/pull-request.md)
   
   If your pull request contains incompatible change, you should also add it to 
`docs/docs/en/guide/upgrade/incompatible.md`
   
   This PR does not contain incompatible changes.
   
   Fix https://github.com/apache/dolphinscheduler/issues/17994


-- 
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]

Reply via email to