Dynflowize environment delete
Fixes #6815,#6187/bz1125398,1125358 - Environment Destroy Dynflow
This commit adds code to orchestrate lifecycle env destroy via dynflow.
In addition to that it adds code to prevent environment deletion if any
of the lifecycle env associations like content hosts and activation keys
#4 Updated by Ivan Necas almost 5 years ago
- Status changed from Closed to New
- Target version deleted (
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
#7 Updated by David Davis almost 5 years ago
Looks like I wrote the code in an another PR but forgot to pull it over to the new PR:
#8 Updated by David Davis almost 5 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.