If I'm not mistaken, the awx-operator uses Github Actions to build and push the awx-operator-bundle and awx-operator-catalog images to quay.io/ansible namespace, and sends a PR to https://github.com/k8s-operatorhub/community-operators/tree/main/operators to add the manifests for the operator for each new release.
I would like the awx-resource-operator to build the bundle and catalog images for itself, as well as send automated PR's to the community catalog more or less in the same way as the awx-operator.
If I'm not mistaken, the awx-operator uses Github Actions to build and push the awx-operator-bundle and awx-operator-catalog images to quay.io/ansible namespace, and sends a PR to https://github.com/k8s-operatorhub/community-operators/tree/main/operators to add the manifests for the operator for each new release.
I would like the awx-resource-operator to build the bundle and catalog images for itself, as well as send automated PR's to the community catalog more or less in the same way as the awx-operator.