Open camilamacedo86 opened 4 years ago
openshift-bot
commented
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
camilamacedo86
commented
3 years ago /remove-lifecycle stale
openshift-bot
commented
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
openshift-bot
commented
3 years ago 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
estroz
commented
3 years ago @camilamacedo86 I think this is done. If not, can you please re-open? Thanks!
camilamacedo86
commented
3 years ago HI @estroz,
I am re-open this one. See the doc: https://master.sdk.operatorframework.io/docs/building-operators/ansible/testing-guide/
It shows have the old layout (before 1.0). See that now we have default and kind. (not test-local). The files are different for 1.0 as well.
So, imo:
estroz
commented
3 years ago /lifecycle frozen
Feature Request
Is your feature request related to a problem? Please describe. For 1.0.0 the molecule directory changes and then, the Ansible Based Operator Testing with Molecule is outdated.
Describe the solution you'd like