Closed geerlingguy closed 4 years ago
I know @leifmadsen has been doing a lot of work to get the scorecard check passing on some of the Ansible-based operators he's working on, so if I run into issues here, check with him also on the CoreOS slack.
I can get mine to pass now. I'll check after lunch to see what you're missing.
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
This issue is no longer marked for closure.
Docs for how to set up validation: https://sdk.operatorframework.io/docs/ansible/reference/advanced_options/#custom-resources-with-openapi-validation (cc @shanemcd).
Now that the operator is being maintained in the Ansible namespace, I am not going to maintain this project anymore (as I consider it a historic artifact which was used to as a base for the ansible-namespace version, and I'm redirecting all issues and PRs to the Ansible-maintained version: https://github.com/ansible/awx-operator
Currently this operator doesn't have a validation section for the CRD, nor a spec CSV with CRD fields defined. I'd like to get all that fixed so this operator can pass the
operator-sdk scorecard
check.