Project

General

Profile

Bug #19926

Puppet module repo deletion has no protection

Added by Josh Pavel about 2 years ago. Updated about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Repositories
Target version:
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

1.) Create a product that contains puppet module repos
2.) Create content views and hosts to use those puppet modules
3.) You are able to delete the puppet repos which orphans the content views and hosts

Expected behavior: if puppet modules are used by published puppet environments, the same protection afforded to RPMs should be offered to puppet modules.

In my specific case, we were moving from using the public puppet forge to a private internal forge that performs a fall-through itself to the public forge. We had previously had the public forget linked directly. When we attempted to migrate to the internal forge, we were permitted to remove the old public puppet repos, and our linked modules disappeared from the content views. On re-adding them, they automatically re-appeared in content views, without having to republish them.

History

#1 Updated by Eric Helms about 2 years ago

  • Legacy Backlogs Release (now unused) set to 258

#2 Updated by Justin Sherrill about 2 years ago

  • Legacy Backlogs Release (now unused) changed from 258 to 250

#3 Updated by Justin Sherrill almost 2 years ago

  • Legacy Backlogs Release (now unused) changed from 250 to 114

Also available in: Atom PDF