for governance reasons, we need to access a remote API to determine if a given kafka topic has been associated with the intended schema artifact before allowing the producer to send messages.
The only place where we can access the kafka topic name to do this check is in the ArtifactResolverStrategy - but this doesn't read the configuration like the serdes and SchemaResolver do, and we need the configuration to pass the url of the remote API.
it should be a simple matter of adding the configure() call to the ArtifactReferenceResolverStrategy with a default noop call, and then call that in the AbstractSchemaResolver configure() after it instantiates the resolver strategy.
Feature or Problem Description
for governance reasons, we need to access a remote API to determine if a given kafka topic has been associated with the intended schema artifact before allowing the producer to send messages.
The only place where we can access the kafka topic name to do this check is in the ArtifactResolverStrategy - but this doesn't read the configuration like the serdes and SchemaResolver do, and we need the configuration to pass the url of the remote API.
it should be a simple matter of adding the configure() call to the ArtifactReferenceResolverStrategy with a default noop call, and then call that in the AbstractSchemaResolver configure() after it instantiates the resolver strategy.