-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Add --ignore-not-found=true to scaffolded undeploy make target #5195
Copy link
Copy link
Open
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.language/ansibleIssue is related to an Ansible operator projectIssue is related to an Ansible operator projectlanguage/goIssue is related to a Go operator projectIssue is related to a Go operator projectlanguage/helmIssue is related to a Helm operator projectIssue is related to a Helm operator projectlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
Milestone
Description
Metadata
Metadata
Assignees
Labels
good first issueDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.language/ansibleIssue is related to an Ansible operator projectIssue is related to an Ansible operator projectlanguage/goIssue is related to a Go operator projectIssue is related to a Go operator projectlanguage/helmIssue is related to a Helm operator projectIssue is related to a Helm operator projectlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.
Feature Request
While deploying the objects in
config/with kustomize, sometimes it goes wrong (user error) and not all the objects are created. When this happens,make undeployfails on the first object that doesn't exist. Its easy to work around, just delete them manually. However this interrupts development flow and is a bit annoying.If we add
--ignore-not-found,make undeploywill always try to delete all the objects./language go
/language ansible
/language helm