Investigate using server side dry-runs also when creating resources #24
Comments
pst
added a commit
that referenced
this issue
Jun 16, 2022
* requires namespace to exist for namespaced resources * requires CRD to exist for custom objects If namespace or CRD does not exist, the server side dry-run result is ignored for the respective resource.
pst
added a commit
that referenced
this issue
Jun 16, 2022
* requires namespace to exist for namespaced resources * requires CRD to exist for custom objects If namespace or CRD does not exist, the server side dry-run result is ignored for the respective resource.
pst
added a commit
that referenced
this issue
Jun 16, 2022
Add server side dry-run before create fix #24
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A PR to create a new namespace referenced a non existing namespace (due to a typo) in a kustomization.yaml
namespaceattribute. The Terraform plan of this change was all green, because the namespace name, while non-existent, was valid. Yet the apply naturally failed trying to create resources in a namespace that did not exist.Currently, server side dry-runs are only used during update. Running create dry-runs should also surface above error during plan.
The text was updated successfully, but these errors were encountered: