Molecule scenarios not generated as documented

[paterczm]

Hello!

I'm following the testing-guide for ansible operator generated with operator-sdk. The doc states that default, test-local and cluster directories/scenarios should be created inside the molecule directory. However, I only see default and kind directories. What am I missing? Should the documentation be updated?

Steps to reproduce:

$ operator-sdk version
operator-sdk version: "v1.30.0", commit: "b794fe909abc1affa1f28cfb75ceaf3bf79187e6", kubernetes version: "1.26.0", go version: "go1.19.10", GOOS: "linux", GOARCH: "amd64"

$ operator-sdk init --domain example.com --plugins ansible
Writing kustomize manifests for you to edit...
Next: define a resource with:
$ operator-sdk create api

$ operator-sdk create api --group cache --version v1alpha1 --kind Memcached --generate-role
Writing kustomize manifests for you to edit...

Actual results:

$ tree molecule/
molecule/
├── default
│   ├── converge.yml
│   ├── create.yml
│   ├── destroy.yml
│   ├── kustomize.yml
│   ├── molecule.yml
│   ├── prepare.yml
│   ├── tasks
│   │   └── memcached_test.yml
│   └── verify.yml
└── kind
    ├── converge.yml
    ├── create.yml
    ├── destroy.yml
    └── molecule.yml

Expected results:

Default, test-local and cluster directories/scenarios should be created inside the molecule directory, as documented.

[everettraven]

@paterczm Thanks for pointing this out! Looking at the git blame of these docs it looks like this particular doc is in need of an update as the last significant change to it was ~3 years ago.

/label kind/documentation

[openshift-ci[bot]]

@everettraven: The label(s) /label kind/documentation cannot be applied. These labels are supported: platform/aws, platform/azure, platform/baremetal, platform/google, platform/libvirt, platform/openstack, ga, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, px-approved, docs-approved, qe-approved, downstream-change-needed, rebase/manual, approved, backport-risk-assessed, bugzilla/valid-bug, cherry-pick-approved, jira/valid-bug, staff-eng-approved. Is this label configured under labels -> additional_labels or labels -> restricted_labels in plugin.yaml?

In response to [this](https://github.com/operator-framework/ansible-operator-plugins/issues/32): >@paterczm Thanks for pointing this out! Looking at the git blame of these docs it looks like this particular doc is in need of an update as the last significant change to it was ~3 years ago. > >/label kind/documentation Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[everettraven]

@paterczm Would you be interested in helping update this documentation?