Project

General

Profile

Actions
Copy link

Feature #9623

closed

add foreman setting to lock puppet environment to content view

Added by Pat Riehecky about 9 years ago. Updated over 4 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Hosts
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

While it may be useful to have the puppet environment completely flexible, it would be nice if there were an optional setting (under settings/katello) to force the puppet environment to match the content view.

I'd expect the majority of the time users want the environment locked to match, but forcing this upon them seems a bit heavy handed. A setting which a foreman admin can enable to force this behavior may reduce the possibility of unexpected user error while still keeping the existing behavior the default.

Actions
Copy link
 #1

Updated by Eric Helms about 9 years ago

  • Triaged changed from No to Yes
Actions
Copy link
 #2

Updated by Eric Helms over 8 years ago

  • translation missing: en.field_release set to 114
Actions
Copy link
 #3

Updated by John Mitsch over 4 years ago

  • Status changed from New to Rejected
  • Target version deleted (Katello Backlog)

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Actions
Copy link

Also available in: Atom PDF