hutiefang76 commented on PR #12443:
URL: https://github.com/apache/seatunnel/pull/12443#issuecomment-6317550884

   Confirmed against `3d6c855f`: Daniel’s pointers match the current submission 
paths. The shared guard is applied in `ReadonlyConfig`, all five 
`ConfigBuilder` map conversions, and the [decrypt 
re-parse](https://github.com/apache/seatunnel/blob/3d6c855f30d0a0b915befbe29abea3e31e6e7bb3/seatunnel-core/seatunnel-core-starter/src/main/java/org/apache/seatunnel/core/starter/utils/ConfigShadeUtils.java#L229).
 The EN/ZH config and REST docs explicitly keep `->` splitting and parser 
normalization; they do not claim byte-for-byte key preservation.
   
   The production changes remain in `seatunnel-api` and 
`seatunnel-core-starter`, with REST and engine coverage in tests. The separate 
metadata-provider follow-up is #12928, which I have handed to @Nikk8091. I will 
keep that out of this PR. CI is still a separate, unsatisfied gate.
   


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