Fix attribute for Smart Proxy Server

[maximiliankolb]

What changes are you introducing?

I came to fix the example user input but stayed to fix the attribute.

Why are you introducing these changes? (Explanation, links to references, issues, etc.)

You can synchronized a CV to a Smart Proxy Server but not from your Foreman Server onto your Smart Proxy that's on your Foreman Server.

Anything else to add? (Considerations, potential downsides, alternative solutions you have explored, etc.)

Checklists

• 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.13/Katello 4.15
• Foreman 3.12/Katello 4.14 (Satellite 6.16)
• Foreman 3.11/Katello 4.13 (orcharhino 6.11 on EL8 only; orcharhino 7.0 on EL8+EL9)
• Foreman 3.10/Katello 4.12
• Foreman 3.9/Katello 4.11 (Satellite 6.15; orcharhino 6.8/6.9/6.10)
• Foreman 3.8/Katello 4.10
• Foreman 3.7/Katello 4.9 (Satellite 6.14)
• We do not accept PRs for Foreman older than 3.7.

[github-actions]

The PR preview for 3571320 is available at theforeman-foreman-documentation-preview-pr-3538.surge.sh

The following output files are affected by this PR:

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

show diff

show diff as HTML

[ekohl]

I'm not entirely sure I agree that you want to sync to a specific server. Server feels like an implementation detail. In theory there could be a whole highly available Pulp cluster running in Kubernetes behind it. Not something we support today, but code should be there to make it a reality.

[maximiliankolb]

In the docs, we always differentiate between "Smart Proxies" and "Smart Proxy Servers". With content views, you can use the Web UI or Hammer CLI to sync them from your Foreman+Katello Server to a Smart Proxy Server. You cannot sync them from your Foreman+Katello Server to the Smart Proxy that runs on your Foreman+Katello Server; it actually comes from there.