Project

General

Profile

Actions

Refactor #6187

closed

Dynflowize environment delete

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

Status:
Closed
Priority:
Normal
Assignee:
Category:
Orchestration
Target version:
Branch:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Related issues 2 (0 open2 closed)

Related to Katello - Bug #6815: I can delete a environment even if it has associationsRejectedPartha Aji07/29/2014Actions
Blocks Katello - Feature #6180: Implement org destroyClosedDavid Davis06/12/2014Actions
Actions #1

Updated by Ivan Necas almost 10 years ago

Actions #2

Updated by David Davis almost 10 years ago

  • Assignee set to David Davis
Actions #3

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 #4

Updated by Ivan Necas over 9 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 #5

Updated by Ivan Necas over 9 years ago

  • Target version set to 54
Actions #6

Updated by David Davis over 9 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 #7

Updated by David Davis over 9 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 #8

Updated by David Davis over 9 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 #9

Updated by David Davis over 9 years ago

  • Related to Bug #6815: I can delete a environment even if it has associations added
Actions #10

Updated by Ivan Necas over 9 years ago

  • Assignee changed from David Davis to Adam Ruzicka

Ok, assigning this to aruzicka, just for auditing purposes, leaving the deletion of associations untouched for now.

Actions #11

Updated by Eric Helms over 9 years ago

  • Bugzilla link set to 1125358
Actions #12

Updated by The Foreman Bot over 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/4571 added
  • Pull request deleted ()
Actions #13

Updated by David Davis over 9 years ago

  • Assignee changed from Adam Ruzicka to Partha Aji
  • Pull request https://github.com/Katello/katello/pull/4563 added
  • Pull request deleted (https://github.com/Katello/katello/pull/4571)
Actions #14

Updated by Partha Aji over 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions #15

Updated by Eric Helms over 9 years ago

  • translation missing: en.field_release set to 13
Actions

Also available in: Atom PDF