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

[ENH] - Use Nebari CLI instead of Python and Pytest fixtures to deploy Nebari in our cloud integration tests #2950

Open
marcelovilla opened this issue Feb 10, 2025 · 0 comments

Comments

@marcelovilla
Copy link
Member

Feature description

Our local integration tests rely on the Nebari CLI to deploy it. On the other hand, our cloud integrations tests (i.e., AWS, Azure and GCP) rely on Pytest fixtures using the Nebari internals to deploy it.

I believe it would be beneficial to be consistent and use the Nebari CLI for our cloud integration tests as well.

Value and/or benefit

Using Pytest fixtures and Nebari internals to deploy it seems like an unnecessary overhead: it makes things harder to debug and maintain. Furthermore, we expect users to use the Nebari CLI to deploy it instead of using Python and importing Nebari submodules that are meant to be private.

Anything else?

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: New 🚦
Development

No branches or pull requests

1 participant