-
Notifications
You must be signed in to change notification settings - Fork 5
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
Standardize abstract_charm.py file with the K8s charm #182
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.
lgtm
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.
please wait for canonical/mysql-router-k8s-operator#328 merge before merging this pr
I am pending decision in K8s before reviewing VM one. |
@paulomach K8s got merged yesterday. Should this follow? |
@taurus-forever no. It's currently out of sync. I rather wait for @shayancanonical to resync it. |
…arm (#339) ## Issue While standardizing code in the router vm charm (canonical/mysql-router-operator#182), there were small minor adjustments that needed to be made in the code in this repo ## Solution Propagate appropriate changes
Issue
The
abstract_charm.py
has diverged with the K8s charm following in support of HACluster charm integration +expose-external
config in the K8s charm.Solution
Standardize the files
Counterpart PR in K8s charm: canonical/mysql-router-k8s-operator#328