[Improvement] [Task-Seatunnel] config file suffix parse error

[Xuzhengz]

Search before asking

• I had searched in the issues and found no similar issues.

What happened

The content of the seatunnel task file uses the result passed upstream, which is in JSON format. However, the file is created with a conf suffix because the variable values were not replaced with the JSON result passed upstream during the validation process of JSONUtils.checkJsonValid

What you expected to happen

When passing the JSON Utils. checkJsonValid checksum, parse the variable value into the result passed upstream

How to reproduce

1. Set a config name for the global parameter and pass in a JSON format seatunnel task configuration information
2. Use ${config} as task configuration in the seatunnel task

Anything else

No response

Version

dev

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

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