-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: ansible update the Molecule with the new structure #26
Comments
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
/remove-lifecycle stale |
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
@camilamacedo86 I think this is done. If not, can you please re-open? Thanks! |
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:
|
/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
The text was updated successfully, but these errors were encountered: