Skip to content
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

deploy each itest in its own model #108

Closed
PietroPasotti opened this issue Nov 29, 2022 · 2 comments
Closed

deploy each itest in its own model #108

PietroPasotti opened this issue Nov 29, 2022 · 2 comments

Comments

@PietroPasotti
Copy link
Contributor

    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.

Originally posted by @sed-i in #103 (comment)

@sed-i
Copy link
Contributor

sed-i commented Nov 29, 2022

Related: juju/python-libjuju#776

@dstathis
Copy link
Contributor

This is old and we are making plans for this sort of thing across all charms.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants