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

"garden delete environment" doesn't delete the project--metadata namespace #1266

Closed
vkorbes opened this issue Oct 15, 2019 · 1 comment · Fixed by #1268
Closed

"garden delete environment" doesn't delete the project--metadata namespace #1266

vkorbes opened this issue Oct 15, 2019 · 1 comment · Fixed by #1268
Labels

Comments

@vkorbes
Copy link
Contributor

vkorbes commented Oct 15, 2019

IMHO the expected behavior for garden delete environment should be to delete everything related to the current project from my cluster. This would be both the project namespace, and the project--metadata namespace.

Local testing indicates the project--metadata namespace stays there.

If there's a reason for that, it should be explained in the command description with garden help delete or in the documentation.

IMHO though, the most intuitive behavior would be to delete both namespaces.

@vkorbes vkorbes added the bug label Oct 15, 2019
@edvald
Copy link
Collaborator

edvald commented Oct 15, 2019

I agree, and I had actually changed this in a branch, where I had other WIP commits. I'll just push that one commit now.

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

Successfully merging a pull request may close this issue.

2 participants