-
Notifications
You must be signed in to change notification settings - Fork 64
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
fix(mysql/user): correctly compare upToDate resourceOptions #71
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
3eadece
to
ace4457
Compare
This comment was marked as resolved.
This comment was marked as resolved.
Signed-off-by: Duologic <jeroen@simplistic.be>
ace4457
to
0f12654
Compare
The SQL provider has been crashlooping on one of my clusters for a couple of days now - I'm guessing this issue is causing that?
|
Exactly, this PR attempts to fix it. |
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.
nice!
Thanks @Duologic. How often do new Docker images get pushed? Apparently the latest build (provider-sql-controller:v0.4.0-2.g916112c) does not include this fix. |
I'd expect that tag to include this fix, but I haven't tried it properly yet, will do early next week. |
I'm seeing the same/similar error again too, my attempted fix didn't solve it. I'm looking at writing a unit test for it now so we can cover this use case. |
Description of your changes
The pointer-compare caused a panic in my test cluster, had another look at the Postgresql
cod, there the actual values are used not the pointers to compare. Also it doesn't
initialize the integer values, so removed that too.
Fixes #
I have:
make reviewable test
to ensure this PR is ready for review.How has this code been tested
Ran
make reviewable test e2e