operator-framework / operator-framework/operator-sdk
Add --ignore-not-found=true to scaffolded `undeploy` make target
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7.7k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
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 undeploy fails 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 undeploy will always try to delete all the objects.
/language go
/language ansible
/language helm
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name a file; start by locating the scaffolded make undeploy target and the kustomize deployment templates. Confirm how the target deletes objects, then add the requested ignore-not-found option so it attempts every deletion, and verify the generated target reflects that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ansible, go, helm, kubernetes
- Domain
- build-system, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100