On Friday, November 21, 2014 4:33:48 PM UTC-6, Eric Sorenson wrote:
Hi Kyle --
On Friday, November 21, 2014 1:46:19 PM UTC-8, Kyle Purdon wrote:
TL:DR Using the --ordering = manifest option does not seem to apply to
module commands.
Using this parameter I would expect puppet to apply
Eric,
Thanks for the response. I spent the weekend looking into puppet class
containment, what a joy!
I am still a bit unclear on applying contain in my situation.
Should I create a wrapper class around my entire manifest and contain the
few things within that? How would I apply this to the
Eric John!
Emacs is the best! Get over it! =)
Anyway,
I do think John is correct, I really was trying to avoid what is clearly
the Puppet way of things by treating resources as executable things and
trying to order them as such. I think the idea of organizing the manifest
into classes and
Hi,
On 11/24/2014 04:04 PM, Kyle Purdon wrote:
Eric John!
Emacs is the best! Get over it! =)
Emacs is nice, but I prefer Debian. (And no, I'm likely younger than
this joke.)
On Monday, November 24, 2014 7:56:34 AM UTC-7, jcbollinger wrote:
Nope, because they are not classes. The
Here is my Vagrantfile if that helps:
Vagrant.configure(2) do |config|
config.vm.provision :shell, :inline =
cd /vagrant/puppet/librarian;
librarian-puppet clean --verbose; librarian-puppet update --verbose
config.vm.provision :shell, :inline = puppet apply
Hi Kyle --
On Friday, November 21, 2014 1:46:19 PM UTC-8, Kyle Purdon wrote:
TL:DR Using the --ordering = manifest option does not seem to apply to
module commands.
Using this parameter I would expect puppet to apply my manifest (site.pp)
in the order it is written (script like
