-
Notifications
You must be signed in to change notification settings - Fork 26
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
update charms.traefik_route_k8s.v0.traefik_route library #103
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, thanks!
|
||
|
||
async def safe_relate(ops_test: OpsTest, ep1, ep2): | ||
# in pytest-operator CI, we deploy all tests in the same model. |
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.
I think deploying all itests in the same model is not a justification but rather something to avoid.
The introduction of deploy_traefik_if_not_deployed
and deploy_charm_if_not_deployed
seems to me like an antipattern that should be avoided.
In the past we were trying out reset
but it wasn't very stable. If we add a preserve
keyword to reset
perhaps we could try again.
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.
Yeah in hindsight I'd avoid all of that. Models are cheap, I keep forgetting that.
Not in this PR though :D
Issue
Fixes #106.
Release Notes
Update the version of the
charms.traefik_route_k8s.v0.traefik_route
library to the latest one.