hutiefang76 commented on PR #12443:
URL: https://github.com/apache/seatunnel/pull/12443#issuecomment-5852196772
@SEZ9 I pushed `ddca53b7a` with the remaining focused REST cases.
`RestUtilTest` now covers a top-level regex key and nested `$`, `:`, `${FOO}`,
quote, and backslash keys through config-shade encryption and decryption,
alongside the existing `->` path and batch-submit cases. It passes 7/7 on JDK
17.
For the actual submit path,
`RestApiSubmitJobConfigShadeDecryptTest#testSubmitJobWithRegexFieldInJson`
sends a JSON POST to `/submit-job` with `^t_nova_.*$` under
`source.schema.fields` and asserts HTTP 200 plus a `jobId`. That test passed in
the six-test HTTP suite. In `JobInfoService.submitJob`, JSON goes through
`RestUtil.buildConfig` and then `ConfigShadeUtils.decryptConfig` before
dispatch; `submitJobs` decrypts each built config too.
The current diff has the guard in `ConfigBuilder.of(Map)`, its adapter path,
`ConfigShadeUtils.processConfig` (used by both decrypt and encrypt, including
`EncryptConfigService`), and `ReadonlyConfig.toConfig()`.
`MetadataProviderManager` and `AssertSink` remain outside this PR, as the
description notes. Quoting only on `BadPath` deliberately keeps previously
valid `->` path behavior; the exact semantics, including quote removal and
whitespace trimming, are in both REST docs. Since this diff spans API, Core,
and Zeta, I kept the `[Config]` title rather than changing it to `[Zeta]`.
The PR description now points to the current tests and scope. The affected
reactor `verify`, Spotless, and diff check passed locally; I have not treated
the unrelated fork CI failures as a green build.
--
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]
