The Puppet Labs Issue Tracker has Moved:

Bug #11023

Cloud provisioner should be able to start puppet run with --environment

Added by Hunter Haugen over 2 years ago. Updated 4 months ago.

Status:Needs DecisionStart date:11/22/2011
Priority:NormalDue date:
Assignee:Hunter Haugen% Done:


Category:cloud provisioner
Target version:-
Keywords: cloud_provisioner Affected URL:
Branch: Affected PE version:

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket may be automatically exported to the ENTERPRISE project on JIRA using the button below:


I noticed that the puppet node scripts will use the “production” environment if Puppet[:environment] is not set, otherwise it will use Puppet[:environment], but how is Puppet[:environment] on the node set? Do we have to pass --environment through to the node?

I wrote code to do this for a client so let me know if I should commit and push it, or let me know how I was doing it wrong.


#1 Updated by Daniel Pittman over 2 years ago

  • Category set to install
  • Status changed from Unreviewed to Needs Decision
  • Assignee set to Hunter Haugen

Hunter, can you put that into a topic branch and issue a pull request – then update this ticket, and assign to Jeff or the general pool. That would help move this forward. Thanks.

#2 Updated by Charlie Sharpsteen 4 months ago

  • Project changed from Cloud-Provisioner to Puppet Enterprise (Public)
  • Category deleted (install)

#3 Updated by Kenn Hussey 4 months ago

  • Category set to cloud provisioner

Also available in: Atom PDF