Change command for Lifecycle and Environment Path

[bangelic]

What changes are you introducing?

Updating command language.

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

The language in two different commands appears redundant.

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.

[bangelic]

@sjha4 Can you take a look at the changes I made here and let me know if this is accurate to what was discussed with Jeremy? Thanks!

[github-actions]

The PR preview for 8546a15 is available at theforeman-foreman-documentation-preview-pr-3533.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

[maximiliankolb]

I made a suggestion based on https://docs.theforeman.org/nightly/Managing_Content/index-katello.html#Creating_a_Lifecycle_Environment_Path_content-management

It's longer but hopefully helpful to readers.

[Lennonka]

Please, @bangelic, always add a link to the Jira issue in the PR description for better context of your changes.
https://issues.redhat.com/browse/SAT-24004

I think you're missing the point of the reported bug. The reporter wants to make the two commands more differentiated because it's not clear how and why they are different. Therefore, using the same --name example for both does not help.

We're creating an LC environment with each command, not the whole path. The LC env. path is a result of the chain of environments. Let's not use "path" in the --name.

Also, we don't have to use underscores in the example text when it's a name. Only labels use underscores. Let's not put them here.

[Lennonka]

Please, also fix the following in the last step. I cannot comment on it directly.
To view the chain of the lifecycle environment path

[sjha4]

For specifying path to add the environment after library, we exposed the path-id parameter in hammer in this PR:
Katello/katello#11268

Might be helpful to document this as well:
hammer-cli-katello]$ hammer lifecycle-environment create --label=test12 --name=test12 --prior-id=1 --organization-id=1 --path-id=13

[Lennonka]

For specifying path to add the environment after library, we exposed the path-id parameter in hammer in this PR: Katello/katello#11268

Might be helpful to document this as well: hammer-cli-katello]$ hammer lifecycle-environment create --label=test12 --name=test12 --prior-id=1 --organization-id=1 --path-id=13

@sjha4 @bangelic The parameter should be documented in Hammer help. I don't think it's particularly helpful glueing this example command to this procedure. We do not document every Hammer parameter in product documentation as users can look it up in Hammer reference help. That's my two cents.

It's also out of the scope of this PR. We're fixing a bug here. :))