Bug Description
During the setup described in this issue, the MLflow charm had to be redeployed to see its HTTPRoute updated with the correct listener for HTTPs on 443 instead of HTTP on 80, after some other charms were updated to enable TLS and integrated.
It is not clear whether it is a bug with the library provided by Service Mesh or if is it this charm not observing events properly, but in any case the charm is handling events as suggested in the library's docstring, so either the library has a bug or its docstring is to be updated with additional event listeners.
The fix should be applied not only to MLflow but also to other MLOps charms that have HTTPRoutes created via the library.
To Reproduce
Follow the link above but deploy the other charms without TLS, to then update them to switch to TLS, for you to see MLflow with the HTTPRoute outdated.
Environment
See the link above.
Relevant Log Output
Additional Context
No response
Bug Description
During the setup described in this issue, the MLflow charm had to be redeployed to see its HTTPRoute updated with the correct listener for HTTPs on 443 instead of HTTP on 80, after some other charms were updated to enable TLS and integrated.
It is not clear whether it is a bug with the library provided by Service Mesh or if is it this charm not observing events properly, but in any case the charm is handling events as suggested in the library's docstring, so either the library has a bug or its docstring is to be updated with additional event listeners.
The fix should be applied not only to MLflow but also to other MLOps charms that have HTTPRoutes created via the library.
To Reproduce
Follow the link above but deploy the other charms without TLS, to then update them to switch to TLS, for you to see MLflow with the HTTPRoute outdated.
Environment
See the link above.
Relevant Log Output
Additional Context
No response