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

Provider should not attempt to delete default namespace #72

Closed
cgbaker opened this issue Aug 26, 2019 · 0 comments · Fixed by #73
Closed

Provider should not attempt to delete default namespace #72

cgbaker opened this issue Aug 26, 2019 · 0 comments · Fixed by #73

Comments

@cgbaker
Copy link
Contributor

cgbaker commented Aug 26, 2019

Referencing the default namespace (e.g., while attaching a quota) will cause the TF provider to attempt to delete the namespace on destroy. This results in a 500 error. There are workarounds for this, but the root issue is that the TF provider should not attempt to delete things that we know a priori cannot be deleted.

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

Successfully merging a pull request may close this issue.

1 participant