Add Flatpak workflow procedures for Satellite

[bangelic]

What changes are you introducing?

Adding Flatpak workflow procedures for Satellite.

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

In reference to https://issues.redhat.com/browse/SAT-30544.

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 (EL9 only)
• 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 41e3ebe is available at theforeman-foreman-documentation-preview-pr-3624.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

[bangelic]

@sjha4 Take a look/review and let me know if we captured what we needed from the Google Doc.

[sjha4]

Is this clear enough to say these 3 are remote templates?

1. Set up Flatpak remote on host
2. Install Flatpak application
3. Log in to Flatpak registry using podman

I'd add a brief description of the 3.

1st runs a REX job on host to add satellite/capsule as a flatpak remote on the host and logs into podman registry and saves the credentials.
2nd runs a REX job to install Flatpak applications on selected host(s)
3rd runs a REX job to login to podman registry and save credentials on the client.

[bangelic]

@sjha4 The more I try to clarify this with what you want me to add, the more I'm not sure we are telling the user what to do here. Should we keep this section using REX templates?

[sjha4]

There are 3 templates admins can use to set up the clients. We should keep it for admins to be able to do what we document right above this using flatpak cli commands..We should even move it above the regular procedure in this section.

[sjha4]

Updated REX templates to be better grouped for UX and follow convention. These should make it clearer in the documentation.

Flatpak - Set up remote on host
Flatpak - Install application on host
Flatpak - Login to registry via podman

[sjha4]

Lets remove --user from here and add a note for context if needed. The --user flag sets up remote and also installs apps in user context on the client. System-wide installs are the default and the REX templates also follow that.