Bug 2166992 - [RFE] Should be able to rename or edit label of a Lifecycle Environment.
Summary: [RFE] Should be able to rename or edit label of a Lifecycle Environment.
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Lifecycle Environments
Version: 6.13.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-02-03 20:03 UTC by Ashish Patil
Modified: 2023-08-03 17:35 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ashish Patil 2023-02-03 20:03:31 UTC
1. Proposed title of this feature request.
 
 - Label name should be allowed to rename/edit if required.
 
Changing the Lifecycle Environment name is possible. But changing the Lifecycle Environment label is not.
 
2. What is the nature and description of the request?
 
 - Nature: Required to rename/edit Label of a Lifecycle Environment.
 
 - Description: While creating a Lifecycle Environment a label name can be different from the name of the environment.
               
   
 On the registered client we can see the label name of the Lifecycle Environment instead Environment name which may create confusion.
 
~~~
# subscription-manager identity
...
...
org name: RedHat
org ID: RedHat
environment name: Development/RHEL9     <------- 'Development' is the label name.
~~~
 
~~~
# hammer lifecycle-environment info --id 2
Id:                          2
Name:                        Production    <------ 'Production' is the name of LCE
Label:                       Development                   
Description:                 Test for label name
Organization:                RedHat
Library:                     false
Prior Lifecycle Environment: Library
Unauthenticated Pull:        false
Registry Name Pattern:
~~~


Note You need to log in before you can comment on or make changes to this bug.