Open asmacdo opened 3 years ago
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle stale
It was added to Golang: https://github.com/operator-framework/operator-sdk/blob/master/testdata/go/v3/memcached-operator/Makefile#L118-L120
We still need to update the Makefile for Ansible/Helm and the new Go+Helm plugin.
c/c @asmacdo @fabianvf @varshaprasad96
/lifecycle frozen
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen
.
If this issue is safe to close now please do so with /close
.
/lifecycle rotten /remove-lifecycle stale
/lifecycle frozen
Done for GO: https://github.com/operator-framework/operator-sdk/blob/master/testdata/go/v3/memcached-operator/Makefile#L126-L128 because of the KB bump
Missing update the Ansible/Helm dockerfile boilerplate only
Let me know if any work needs to be done on this issue @camilamacedo86 I see it's a Good First Issue
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