Project

General

Profile

Actions

Feature #24596

closed

Provide the ability to delete a lifecycle environment from the middle of an existing path

Added by Justin Sherrill over 6 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Category:
Lifecycle Environments
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1614927

1. Proposed title of this feature request

[RFE] Provide the ability to delete a lifecycle environment from the middle of an existing path

2. What is the nature and description of the request?

It is currently not possible to remove a lifecycle environment from the beginning or middle of an existing lifecycle environment path.

For example if the current lifecycle environments (in order) are
Dev -> Test -> Staging -> Prod

and you wish to remove Staging such that the new list (in order) is
Dev -> Test -> Prod

it is not currently possible to achieve this

3. Why does the customer need this? (List the business requirements here)

The customer supports various distinct environments in their organization. Some environments needs change over time, and this would allow them to remove lifecycle environments that are deemed no longer necessary, by the different environment stakeholders.

4. How would the customer like to achieve this? (List the functional requirements here)

Make it possible, via the gui and hammer to remove a lifecycle environment from the path, in such a way as the previous environment is now linked instead to the latter environment.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

Try to remove "Staging" as per the example in #2

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

None found

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

ASAP

9. Is the sales team involved in this request and do they have any additional input?

No

10. List any affected packages or components.

Satellite 6.3.2
- API
- Hammer
- GUI

11. Would the customer be able to assist in testing this functionality if implemented?

yes

Actions #1

Updated by The Foreman Bot over 6 years ago

  • Status changed from New to Ready For Testing
  • Assignee set to Justin Sherrill
  • Pull request https://github.com/Katello/katello/pull/7620 added
Actions #2

Updated by Jonathon Turel over 6 years ago

  • Target version set to Katello 3.9.0
  • Triaged changed from No to Yes
Actions #3

Updated by Justin Sherrill over 6 years ago

  • Status changed from Ready For Testing to Closed
Actions

Also available in: Atom PDF