Users cannot push containers to docker type repositories with upstream URL synced to Foreman+Katello (SAT-44672)

[jsvarova]

Implementing feedback from issue #4776.

• I am okay with my commits getting squashed when you merge this PR.
• I am familiar with the contributing guidelines.

Please cherry-pick my commits into:

• Foreman 3.18/Katello 4.20 (Satellite 6.19)
• Foreman 3.17/Katello 4.19
• Foreman 3.16/Katello 4.18 (Satellite 6.18; orcharhino 7.6 and 7.7)
• Foreman 3.15/Katello 4.17
• Foreman 3.14/Katello 4.16 (Satellite 6.17; orcharhino 7.4; orcharhino 7.5)
• Foreman 3.13/Katello 4.15 (EL9 only)
• Foreman 3.12/Katello 4.14 (Satellite 6.16; orcharhino 7.2 on EL9 only; orcharhino 7.3)
• We do not accept PRs for Foreman older than 3.12.

[github-actions]

The PR preview for 9a49c29 is available at theforeman-foreman-documentation-preview-pr-4792.surge.sh

The following output files are affected by this PR:

• Managing_Content/index-foremanctl-katello.html
• Managing_Content/index-foremanctl-orcharhino.html
• Managing_Content/index-foremanctl-satellite.html
• Managing_Content/index-katello.html
• Managing_Content/index-orcharhino.html
• Managing_Content/index-satellite.html

show diff

show diff as HTML

[maximiliankolb]

one small suggestion. About git commit messages: we have a link to a blog article somewhere in CONTRIBUTING.md that explains how to phrase them.

I have adjusted the title of your PR to make it more descriptive too.

[maximiliankolb]

style-wise LGTM

[jsvarova]

Hello Max, I read through https://cbea.ms/git-commit/#seven-rules (as pointed out by Lennonka in my other PR as well). I'll keep in in mind!

@ianballou Could you please provide the technical review when time allows? Thank you!

[ianballou]

The behavior is a little more nuanced, you can only push containers to repositories created by the container push workflow. To be technical, any repository created by using the container registry endpoints can be pushed to, and repositories created by the general repositories endpoints cannot be pushed to. Pretty much this means that users dealing with "container push" repositories should interact with them only via podman (or docker), unless the publish them into a content view.

So while the above gets to the gist of the situation, it omits that you cannot create an empty repo with no upstream URL and push content to it, which users may try.