We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
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.
deploy_traefik_if_not_deployed
deploy_charm_if_not_deployed
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.
reset
preserve
Originally posted by @sed-i in #103 (comment)
The text was updated successfully, but these errors were encountered:
Related: juju/python-libjuju#776
Sorry, something went wrong.
This is old and we are making plans for this sort of thing across all charms.
No branches or pull requests
The introduction of
deploy_traefik_if_not_deployed
anddeploy_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 apreserve
keyword toreset
perhaps we could try again.Originally posted by @sed-i in #103 (comment)
The text was updated successfully, but these errors were encountered: