[
https://issues.apache.org/jira/browse/KAFKA-7225?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16566297#comment-16566297
]
ASF GitHub Bot commented on KAFKA-7225:
---------------------------------------
rayokota opened a new pull request #5445: KAFKA-7225 - Pretransform validated
props
URL: https://github.com/apache/kafka/pull/5445
If a property requires validation, it should be pretransformed if it is a
variable reference, in order to have a value that will properly pass the
validation.
### Committer Checklist (excluded from commit message)
- [ ] Verify design and implementation
- [ ] Verify test coverage and CI build status
- [ ] Verify documentation (including upgrade notes)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
> Kafka Connect ConfigProvider not invoked before validation
> ----------------------------------------------------------
>
> Key: KAFKA-7225
> URL: https://issues.apache.org/jira/browse/KAFKA-7225
> Project: Kafka
> Issue Type: Bug
> Components: KafkaConnect
> Affects Versions: 2.0.0
> Reporter: Nacho Munoz
> Assignee: Robert Yokota
> Priority: Minor
>
> When trying to register a JDBC connector with externalised secrets (e.g.
> connection.password) the validation fails and the endpoint returns a 500. I
> think that the problem is that the config transformer is not being invoked
> before the validation so trying to exercise the credentials against the
> database fails. I have checked that publishing the connector configuration
> directly to the connect-config topic to skip the validation and restarting
> the server is enough to get the connector working so that confirms that we
> are just missing to call config transformer before validating the connector.
> Please let me know if you need further information.
> I'm happy to open a PR to address this issue given that I think that this is
> easy enough to fix for a new contributor to the project. So please feel free
> to assign the resolution of the bug to me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
