Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding new concepts and procedures for Multi CV hosts and AKs #3609

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

bangelic
Copy link
Contributor

What changes are you introducing?

New procedures and concepts pertaining to
multiple content view environments for hosts
and activation keys related to https://issues.redhat.com/browse/SAT-20897

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

New features for 6.17.

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

A separate PR for the same ticket will be submitted
to update existing documentation.

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.

@bangelic
Copy link
Contributor Author

@jeremylenz This PR is supposed to cover the new procedures and concepts from our shared Google Doc. Take a look and make suggestions and comments because we had a lot of content and I want to make sure nothing got overlooked. We can discuss the content needed for the existing documentation to be put in a separate PR. This is just the new procedures and concepts.

Copy link

github-actions bot commented Jan 23, 2025

@Lennonka Lennonka added the Waiting on contributor Requires an action from the author label Jan 29, 2025
@bangelic bangelic force-pushed the bangelic-SAT-20897-Update-docs-for-MultiCV-hosts-and-AKs-new-docs branch from 9d3fdfa to da5911b Compare January 30, 2025 01:33
@pr-processor pr-processor bot added Needs re-review and removed Waiting on contributor Requires an action from the author labels Jan 30, 2025
@bangelic bangelic force-pushed the bangelic-SAT-20897-Update-docs-for-MultiCV-hosts-and-AKs-new-docs branch from da5911b to c8782e6 Compare January 30, 2025 19:37
@github-actions github-actions bot added Needs tech review Requires a review from the technical perspective Needs style review Requires a review from docs style/grammar perspective Needs testing Requires functional testing labels Jan 30, 2025
@bangelic bangelic force-pushed the bangelic-SAT-20897-Update-docs-for-MultiCV-hosts-and-AKs-new-docs branch from 4d92e7d to f00c1c4 Compare January 31, 2025 18:56
@bangelic bangelic force-pushed the bangelic-SAT-20897-Update-docs-for-MultiCV-hosts-and-AKs-new-docs branch from f00c1c4 to ea226ec Compare February 3, 2025 22:04
The `allow_multiple_content_views` setting controls whether hosts and activation keys can be assigned to multiple content view environments.
By default, this feature is disabled, limiting assignments to a single content view environment.
Enabling the setting allows you to assign multiple content view environments to both hosts and activation keys.
For more information on content settings, see {AdministeringDocURL}general_settings_information_[General settings] in _{AdministeringDocTitle}_.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Doesn't the link also need updating so it says content settings and not general?

+
[options="nowrap" subs="+quotes"]
----
$ hammer activation-key info --id _[1,2,3]_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

--id is just a single number, not an array.

I see elsewhere in the docs we do it like this:

Suggested change
$ hammer activation-key info --id _[1,2,3]_
$ hammer activation-key info --id _My_Activation_Key_ID_

+
[options="nowrap" subs="+quotes"]
----
$ hammer host info --id _[1,2,3]_
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
$ hammer host info --id _[1,2,3]_
$ hammer host info --id _'My_Host_ID'_

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs style review Requires a review from docs style/grammar perspective Needs tech review Requires a review from the technical perspective Needs testing Requires functional testing
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants