-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Set db-operator version on database CR during full reconcile #50
Conversation
88353e7
to
f8dd873
Compare
982e015
to
4ac48bd
Compare
60b255a
to
d54639d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One small thing
But also, CI has failed, so it would be nice to check what's wrong |
d54639d
to
9df1eef
Compare
Well, it looks like it's working as expected. 😅
Can I somehow insert another image to the CI? |
Ah, sure, we need to release the db-operator versions first, sorry |
@bobertrublik |
Hey, I added a migration plan to the README but I don't fully understand how the NOTES.txt works. At the top there is the following text
but how does it know which version is breaking and which is not? 😅 |
Just replace
with something like
|
I hope this looks fine for you. 🙂 |
I had to add a namespace environment variable to allow db-operator to retrieve the namespace in which it runs in. Other than that I simply added a new field
version
to theDatabase
CR.