[ENH] - Use Nebari CLI instead of Python and Pytest fixtures to deploy Nebari in our cloud integration tests #2950
Labels
area: CI/CD 👷🏽♀️
area:developer-experience 👩🏻💻
area: testing ✅
Testing
type: enhancement 💅🏼
New feature or request
Milestone
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
The text was updated successfully, but these errors were encountered: