Bug 2270126

Summary: Update Lifecycle Environment documentation for creating Lifecycle Environment path using CLI procedure.
Product: Red Hat Satellite Reporter: Akash Badak <abadak>
Component: Lifecycle EnvironmentsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 6.14.0CC: bangelic, chrobert
Target Milestone: UnspecifiedKeywords: Documentation, MigratedToJIRA, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 17:26:13 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Akash Badak 2024-03-18 14:12:07 UTC
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.14/html/managing_content/managing_application_lifecycles_content-management#Creating_a_Lifecycle_Environment_Path_content-management

Section Number and Name: 7.3. Creating a Lifecycle Environment Path


Describe the issue: "CLI Procedure" seems to be using effectively the exact same command  to do two different things. It says

To create an environment path, enter the hammer lifecycle-environment create command and specify the Library environment with the --prior option:

# hammer lifecycle-environment create \
--name "Environment Path Name" \
--description "Environment Path Description" \
--prior "Library" \
--organization "My_Organization"
Optional: To add an environment to the environment path, enter the hammer lifecycle-environment create command and specify the parent environment with the --prior option:

# hammer lifecycle-environment create \
--name "Environment Name" \
--description "Environment Description" \
--prior "Prior Environment Name" \
--organization "My_Organization"

Note: Essentially Applies for all satellite version documentation.

Suggestions for improvement: 

1] In the first case which creates a new Environment Path, it should not be necessary to include ' --prior "Library" '. The command knows that it has to create a new Environment Path simply from the fact that the one referred to does not exist, so this option seems to be redundant.

2]  In second command, Since Lifecycle is already created and we want to add another Lifecycle environment path to it, then we can mention new Lifecycle environment in  "--name "Environment Path Name"  and prior to "--prior "Previously created LCE" '

So for the first use case, where we say "--name" we mean the Lifecycle Path name itself, in the second apparently we mean the name of the new lifecycle environment we are adding to the Path. Document should not have Two identical commands where the same option refers to two different things depending on context.

3] The command is specifying , if you do not have any prior environments then use Library and if you have any 'prior' environment and want to specify it then you can specify.


Additional information:

Comment 2 Eric Helms 2024-06-06 17:26:13 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.

Comment 3 Red Hat Bugzilla 2024-10-05 04:27:28 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days