-
Notifications
You must be signed in to change notification settings - Fork 3
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
chore: remove mysql relation to drop MariaDB support #207
Conversation
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.
Should we also update the bundle.yaml files of the repo having mariadb?
the CI is getting stuck at the end of tests execution, I filed #209 to investigate and 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.
Thanks @NohaIhab, just a tiny comment, other than that LGTM. Thanks for removing this unnecessary thing!
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.
Thanks @NohaIhab ! I tested this by deploying the katib-db-manager charm form this PR and tried using the relation juju relate katib-db-manager:mysql <another charm>
and I got:
ERROR application "katib-db-manager" has no "mysql" relation
which confirms the relation is not supported anymore.
Then I added the relational-db
relation just to ensure that relation was not affected by this change and it works.
CKF 1.8 dropped support for MariaDB, which means the charm has to drop all the code that handles this relation.
Summary
mysql
relation