Closed jniebuhr closed 1 year ago
Thanks a lot for your contribution @jniebuhr, it is certainly something required. during my first review I noticed there is no specific test for this new functionality, do you mind adding one? 🙏 it is important for the project to keep the test bed as good as possible.
Looking forward to land this
Also it looks IT test does not pass, can you please take a look at well. Thanks a lot.
@purbon Thanks for the review, I'm adding some tests and fixing the integration tests and will update the PR in a bit.
@purbon I've repaired the failing tests and added some new ones. Also squashed it all into one commit. Could you review again?
Hi @jniebuhr, thanks again for your contributions and help. Sorry, I could not go back here faster, but last week I was wiped out in bed.
I see you started adding some tests, sadly the new functionality still breaks a few things like the still missing implementation for KsqlDB. But we're in a good direction.
There are a couple of other things, we could probably improve, but for now, I think I will take it from here and add a patch for KsqlDB, hopefully, that is ok for you.
This functionality will be available in the next release, check out the main page for info.
Thanks again for your help and valuable contributions.
Hi @purbon, thanks for the feedback. Sure you can integrate it into the other merge request. I have not implemented it for anything other than Connect but it shouldn't throw any errors since there's no sync action generated for those.
I'm in the process of merging this manually now, as said it is going to be in upcoming release anytime.
released under https://github.com/kafka-ops/julie/releases/tag/v4.4.1
Please check if the PR fulfills these requirements
[x] The commit messages are descriptive
[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[x] An issue has been created for the pull requests. Some issues might require previous discussion.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Fixes #541
What is the current behavior? (You can also link to an open issue here) There are only creates or deletes on connectors, no updates.
What is the new behavior (if this is a feature change)? Connector artefacts get a hash of their config. This hash is calculated from the cluster state or persisted in the julie state. If an artefact already exists, the hash is compared and a sync action is added to the plan if necessary.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) No