candidate: rhbk-ha-cluster

RanabirChakraborty commented 4 weeks ago

17-10-2024

Content Viability

[x] must support a “business-viable” use case
[x] isn’t just a demo
[x] is production-ready, as in able to run in Ansible Controller “as-is”
[x] provides a solution an end-to-end automation use case and brings value to our customers

Content Duplication

[x] use case addressed by the content isn’t covered by another validated content collection already - to the best of our knowledge

Content Conformity

[x] is packaged as a content collection - see the Collection Requirements Checklist
[x] is YAML only (Exception: if plugin(s) included are necessary for this specific use-case and are not generic enough for a certified collection)
[x] if there is a plugin(s), it is not a duplicate of something from a certified or supported collection - to the best of our knowledge
[x] supported plugin/module used in a validated role is noted as a dependency

Content Compliance

[x] no known policy or legal reason for why the content shouldn’t be published
[x] README contains information about the purpose of the collection and how to install it
[x] README contains a link to the collection license file
[x] README contains general usage and requirements information such as required versions of ansible-core and Python, and other required libraries or SDKs
[x] install / requirements.yml information all points to Automation Hub, not a Github repo
[x] Repo is self-certified with the OpenSSF Best Practices and has the OpenSSF Best Practices Badge
[x] Has 2 or more active maintainers listed in a CODEOWNERS file.
[x] Has an approved OSI license
[x] Content falls logically into one of these domains - infra, security, network, cloud, edge
[ ] (If internal content) Content has been or is being migrated into the redhat-cop Github org

Content Testing/Validation

[x] runs ansible-lint “Production” profile in an active Github workflow on the repository
[x] passes the ansible-lint “Production” profile
[x] ansible-lint.yml file (if present) only contains justified ignores - with a comment explaining the need for each ignore

djdanielsson commented 2 weeks ago

the name is not very clear, I also wonder if cloud is better then infra due to it having aws in the name.

djdanielsson commented 2 weeks ago

also this is not in the correct layout for a collection

RanabirChakraborty commented 1 week ago

@djdanielsson Can you please review it now and let us know how do you think about it?

ansible / validated-content-discussion