Project

General

Profile

Actions
Copy link

Bug #7595

closed

Only looking in one environment for class import

Added by Julien Abbé over 9 years ago. Updated over 9 years ago.

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

Description

Because import all classes in each environment is really long, we should be able to select one environment to parse and import. No just looking in all env and select one to update classes

Files

Screenshot from 2014-09-23 14_44_27.png View Screenshot from 2014-09-23 14_44_27.png 69.2 KB Dominic Cleal, 09/23/2014 09:45 AM
Actions
Copy link
 #1

Updated by Dominic Cleal over 9 years ago

#4423 in Foreman 1.5.0 allows this, see the attached screenshot.

Does that solve the problem?

Actions
Copy link
 #2

Updated by Julien Abbé over 9 years ago

If it can be called throught API or rake task, yes
Is It ?

Actions
Copy link
 #3

Updated by Dominic Cleal over 9 years ago

  • Status changed from Feedback to Resolved

For the API, you have something like https://foreman.example.com/api/v2/smart_proxies/1/environments/1/import_puppetclasses (http://theforeman.org/api/apidoc/v2/environments/import_puppetclasses.html), though #6856 means it doesn't have the speed advantage yet.

For the rake task, use foreman-rake puppet:import:puppet_classes[batch,production]

Actions
Copy link

Also available in: Atom PDF