Bug 2215117

(In reply to Sandra McCann from comment #0)
> Description of problem:
> Customers are finding uncertified collections instead of the certified ones
> and installing them from galaxy.

There is no "uncertified" version of redhat.satellite on Galaxy.
(There is theforeman.foreman, but that's a different namespace etc, even if it contains largely the same content).

> Add a note in the readme to specify the collection must be installed from AH.

https://github.com/RedHatSatellite/satellite-ansible-collection/#installation lists two installation options: AH and RPM.
Both are supported in the Satellite context.
For Tower/AAP customers would not get the RPM without also having the Satellite product repos enabled there, which is unsupported in that context.

Sandra, what exact changes do you ask us to do to our documentation?

Hi egolov - 

See the jira issue for details. The original request was to add this collection to docs.ansible.com because customers aren't finding it. It's possible they are installing the foreman one by mistake? Anyway, we don't want to add more certified collections to the community package, so the thought was to add a note 'somewhere' that would clarify which is the correct collection.

Perhaps then the solution would be to put a note on the foreman collection to say Red Hat customers should install the certified redhat.satellite collection instead.
What do you think?

Hi Sandra,

(In reply to Sandra McCann from comment #2)

> See the jira issue for details. The original request was to add this
> collection to docs.ansible.com because customers aren't finding it.

My TL;DR reading of the Jira issue is "customers don't find certified collections, because those are only listed on AH which is behind a log-in and thus not listed in Google and co".

> It's possible they are installing the foreman one by mistake?

Technically? Sure.
I thought, however, the fact that the namespaces differ was exactly for the users to differentiate between community and supported?
And this logic also applies to Katello instead of Satellite, oVirt instead of RHV, OKD instead of OpenShift, etc?

> Anyway, we don't want to add more certified collections to the community package

I can understand that, as they are not community ones.

> so the
> thought was to add a note 'somewhere' that would clarify which is the
> correct collection.

I think the 'somewhere' is the important part here

> Perhaps then the solution would be to put a note on the foreman collection
> to say Red Hat customers should install the certified redhat.satellite
> collection instead.
> What do you think?

I would really prefer not to place any pointers at customer-only, paid-for content in our upstream projects/documentation/etc.

Would a solution be to allow the redhat.* namespace to also be published on galaxy.ansible.com, which is indexed by search engines and then in the redhat.satellite README note that *support* is only available if you got the content from AH or via an RPM?
(Which is already the case, as the collection can also be cloned from https://github.com/RedHatSatellite/satellite-ansible-collection and would *technically* work, but not be supported by RH)

So changing what gets added to galaxy is not something I can decide on. I'm not even sure who to ask to approve that change. I thought all certified collections had to be on galaxy already, but I guess that means it's the foreman version and you're proposing adding the redhat.satellite one as well?

Yeah, the version with the theforeman.foreman naming is on Galaxy and redhat.satellite (which is really just the same bits with a few files removed and a few adjusted with sed 's/foreman/satellite/') is on AH.

There is no `redhat` namespace on Galaxy that we could use today.

Other (partner) namespaces don't have that problem, as they can use the same name in both realms.