Vinicius D. Cerutti

Hi @arjxn-py definetly, to reproduce you will need to follow the deploy on DO docs to some extent, https://www.nebari.dev/docs/how-tos/nebari-do The exact version I used was `nebari==2024.5.1` but it should show...

This issue proabably has two things to address: - Repalce the `required_variables` as suggested; - And possible add some kind of masking to the values, if they show up after...

feel free to open a PR, even if its a draft :smiley:

No worries, I am glad all worked in the end :100: . I also should've mentioned that as well next time feel free to ask, as this will help us...

good point, @pt247; I was only considering including the playwright/cypress installation and test execution commands. But its a really neat idea to also incorporate the deploy/init structures.

Thanks @pt247, I was about to assign you to this as well 😄

@Adam-D-Lewis has provided a good direction, but to sumirize, basically: We should include a new action file, copying mostly what's already in place under `test_local_integration` and replacing the source installation...

Hi @krassowski, you are completely right, the main issue for the delayed destroy execution, is that usually, terraform relies on the response time from the Kubernetes API, which usually is...

> Stage=stages/07-kubernetes-services failed to fully destroy ERROR: not all nebari stages were destroyed properly. For cloud deployments of Nebari typically only stages 01 and 02 need to succeed to properly...

I did a quick glance and the issues seems to be in the argo-workflow-controller package itself, it looks like it does not suport the roles structure, only the groups