1. Proposed title of this feature request

Content view publish role needs to be idempotent

2. What is the nature and description of the request?

The redhat-satellite-4.0.0 - content_view_publish role is not idempotent. The redhat.satellite.content_view_publish role should publish one time if we set for instance the version of the CV/CCV or the current environment life cycle.

3. Why does the customer need this? (List the business requirements here)

We need to automate work on the satellite, particularly the creation of content from the repo until CV creation (including publishing) and CCV (including the previous CV created and published and publishing and promoting the CCV).

When adding content, you need to be able to be sure that this content is included. Hence, expect that when the definition in the CCV is defined, the CCV will include the CV and publish the content one time, and be sure that it is as the state is guaranteed by Ansible when it is done regularly.

Currently, the CV or CCV is republished each time the code is executed, but it should be the case that it is against the idempotency of the code provided by the red hat collection.

The difficulties with AAP and the Red Hat satellite collection are to provide a way of ensuring that whatever the number of times the code is executed gets the same result as expected by the code written. Currently, the promotion and publication are not easy with this collection, unfortunately.