Remove unused mysql relation
#73
Labels
enhancement
New feature or request
Comments
|
Thank you for reporting us your feedback! The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5484.
|
DnPlas
added a commit
that referenced
this issue
Apr 8, 2024
The charm has a mysql relation that is not used as it is provided by the mariadb charm which is no longer supported. The other alternative is to use the relational-db relation to relate to mysql-k8s charm, but due to #64, it is not possible. In #71 it was decided that instead of an external DB provider, the mlmd charm will use the SQLite implementation it has been using for a while. In PR#72 the charm code has been modified to exclusively use SQLite. Fixes #73
DnPlas
added a commit
that referenced
this issue
Jun 21, 2024
The charm has a mysql relation that is not used as it is provided by the mariadb charm which is no longer supported. The other alternative is to use the relational-db relation to relate to mysql-k8s charm, but due to #64, it is not possible. In #71 it was decided that instead of an external DB provider, the mlmd charm will use the SQLite implementation it has been using for a while. In PR#72 the charm code has been modified to exclusively use SQLite. Fixes #73
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
The charm has a
mysqlrelation that is not used as it is provided by themariadbcharm which is no longer supported. The other alternative is to use therelational-dbrelation to relate tomysql-k8scharm, but due to #64, it is not possible.In #71 it was decided that instead of an external DB provider, the
mlmdcharm will use the SQLite implementation it has been using for a while. In PR#72 the charm code has been modified to exclusively use SQLite.What needs to get done
Remove the
mysqlrelation from themetadata.yamlfileDefinition of Done
The metadata.yaml file does not have the relation.
The text was updated successfully, but these errors were encountered: