Project

General

Profile

Actions
Copy link

Refactor #14618

closed

Refactor plugin initialization and loading

Added by Anonymous over 8 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Core
Target version:
1.12.0
Difficulty:
Triaged:
Bugzilla link:
Pull request:
https://github.com/theforeman/smart-proxy/pull/390
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

to allow for:
- support for multiple simultaneous providers
- programmatically defined settings
- custom validators
- ability to customize module loading

Related issues 3 (0 open — 3 closed)

Related to Smart Proxy - Bug #15025: Warning on startup: Couldn't find settings file config/settings.d/foreman_proxy.ymlClosed05/12/2016Actions
Related to Smart Proxy - Bug #15110: Default setting values used for module initialization aren't being marked as "default" when they are logged.Closed05/20/2016Actions
Blocks Smart Proxy - Feature #13667: puppet_proxy and puppetca modules load puppet gem in puppet 4.0 and higher environments Closed02/11/2016Actions
Actions
Copy link
 #1

Updated by Anonymous over 8 years ago

  • Category set to Core
Actions
Copy link
 #2

Updated by Dominic Cleal over 8 years ago

  • Status changed from Assigned to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/390 added
Actions
Copy link
 #3

Updated by Dominic Cleal over 8 years ago

  • Blocks Feature #13667: puppet_proxy and puppetca modules load puppet gem in puppet 4.0 and higher environments added
Actions
Copy link
 #4

Updated by Dominic Cleal over 8 years ago

  • Translation missing: en.field_release set to 136
Actions
Copy link
 #5

Updated by Anonymous over 8 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions
Copy link
 #6

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #15025: Warning on startup: Couldn't find settings file config/settings.d/foreman_proxy.yml added
Actions
Copy link
 #7

Updated by Dominic Cleal over 8 years ago

  • Related to Bug #15110: Default setting values used for module initialization aren't being marked as "default" when they are logged. added
Actions
Copy link

Also available in: Atom PDF