--dryRun option of julieOps does not detect schema changes & compatability with schema registry.

[hansh0801]

Is your feature request related to a problem? Please describe. A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I am trying to manage schema in schema registry through julieops. As I continued testing, I realized that the dryrun option for schema changes didn't work as I expected. Perhaps julieops is a problem caused by not tracking the schema state.

• Even though the schema has already been applied, it looks like the schema is being recreated.

  1. Apply schema to topic
  2. Without changing anything, add the --dryrun option again to check whether the schema is applied.
  3. The schema has already been applied, but I can see com.purbon.kafka.topology.actions.topics.RegisterSchemaAction log

• Schema compatibility cannot be tracked.

  1. It would be nice to be able to track schema compatibility in dryrun .
  2. I found that it aws discussed at https://github.com/kafka-ops/julie/issues/223

Describe the solution you'd like A clear and concise description of what you want to happen.

• Track the schema state, so that can track what changes are made during --dryrun option.
• could check the compatibility of the schema, maybe compatibility can be checked with https://docs.confluent.io/platform/current/schema-registry/develop/using.html#sr-test-compat-latest api.

[Sounie]

This is the type of functionality that was proposed in an old PR (254).

The organisation that I work for is using an old fork that includes that PR.

@purbon this is my explanation for not just upgrading to the latest release, that you asked about on another issue that seems to have been deleted.

[purbon]

Hi @Sounie that is fine, but for this purpose, backporting will not really help. I would suggest you can grab the related commits from here and just use it in. What do you think?

[hansh0801]

When will the feature request be applied? I want to check the old PR.