Refactor #6187: Dynflowize environment delete - Katello - Foreman

Custom queries

All issues closed in the last 3 weeks
Assigned to me
Closed Issues without Release
Easy and Trivial Issues
Errata Management
Good first issues - Foreman core
Issues without Bugzilla
Katello 4.11.0 TODO
Katello 4.12.0 TODO
Mine
My issues closed in the last 3 weeks
open docker issues
open docker issues 2.1
Open Features
Open Katello issues by target version
Open Pull Requests
Stale
Team Brad Backlog
Trackers
Untriaged
Untriaged and opened in the past two weeks

Actions

Copy link

Refactor #6187

closed

Dynflowize environment delete

Added by Ivan Necas almost 10 years ago. Updated almost 6 years ago.

Status:

Closed

Priority:

Normal

Assignee:

Partha Aji

Category:

Orchestration

Target version:

Katello 2.0

Branch:

Difficulty:

Triaged:

Yes

Bugzilla link:

1125358

Pull request:

https://github.com/Katello/katello/pull/4563

Fixed in Releases:

Found in Releases:

Red Hat JIRA:

Related issues 2 (0 open — 2 closed)

	Related to Katello - Bug #6815: I can delete a environment even if it has associations	Rejected	Partha Aji	07/29/2014			Actions
	Blocks Katello - Feature #6180: Implement org destroy	Closed	David Davis	06/12/2014			Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Ivan Necas almost 10 years ago

Blocks Feature #6180: Implement org destroy added

Actions

Copy link

Updated by David Davis almost 10 years ago

Assignee set to David Davis

Actions

Copy link

Updated by David Davis almost 10 years ago

Status changed from New to Closed

The env destroy doesn't require dynflow. It doesn't touch any backend services. There was some code I wrote/fixed as part of this bug but I'll just move that code to the PR for #6180.

Actions

Copy link

Updated by Ivan Necas almost 10 years ago

Status changed from Closed to New
Target version deleted (48)

I don't think this is reason for not having the lifecycle enevironment destroy action. Two reasons for having it:

1. destroying the resoruces under the lifecycle environment: consumers, content view versions

2. having the action recorded in the foreman tasks for auditing purposes

Actions

Copy link

Updated by Ivan Necas almost 10 years ago

Target version set to 54

Actions

Copy link

Updated by David Davis almost 10 years ago

@ivan, content view versions and consumers aren't tied directly to environments. I'll have to take a look at the code again but I don't believe you can delete an environment if it has content_view_environments.

Actions

Copy link

Updated by David Davis almost 10 years ago

Looks like I wrote the code in an another PR but forgot to pull it over to the new PR:

https://github.com/Katello/katello/pull/4324/files#diff-186d05e79248a368ffb5ff36269a9ea2R39

Actions

Copy link

Updated by David Davis almost 10 years ago

I've created a bug to address the deleting of environments with associations in the short term.

Longer term, maybe we can develop something that would at least warn users if environments have content hosts, etc. This would of course rely on dynflow. Maybe we could even allow users to choose whether to reassign or destroy associations like the content view remove code.

Actions

Copy link