I want to do a syntax check of all our managed puppet manifests in rspec.
It's an easy way to generate build reports for use in a CI.
My first attempt looks like this:
Puppet::Face[:parser, '0.0.1'].validate('puppet/manifests/site.pp')
But this throws the following error:
Puppet::Erro
I know this is old, but ran into it due to some concat dep cycle errors I
had.
But the way you can do this without stages is with collections. If you're
using the apt module, you'd
Class['myrepositories'] -> Apt::Source<| |>
On Friday, June 7, 2013 2:59:17 PM UTC-7, Jakov Sosic wrote:
>
> On
rovide containment for dependencies.
anchor { "apt::source::${name}":
require => Class['apt::update'],
}
Could that do it? That's the Class[apt::update] ->
Anchor[apt::source::puppetlabs] -> Exec[apt_update] cycle right?
On Fri, May 10, 2013 at 10:07 AM,
f I then run 'apt-get update' and rerun it,
no errors.
On Fri, May 10, 2013 at 7:25 AM, jcbollinger wrote:
>
>
> On Thursday, May 9, 2013 10:23:25 PM UTC-5, Nan Liu wrote:
>
>> On Thu, May 9, 2013 at 11:52 AM, James Kyle wrote:
>>
>>> I've run into s
I've run into several incidences where a module attempts to install a
package before the apt::source is added or an update is run. Result is a
bunch apt errors and explosions.
Basically what should be done is all the apt::sources are added and and an
update run _before_ any packages are install
:
>
>
>
> On Wednesday, May 8, 2013 8:06:27 PM UTC-5, James Kyle wrote:
>>
>> I started getting the following errors from my puppet master:
>>
>> > Error: Could not retrieve catalog from remote server: Error 400 on
>> SERVER: Invalid parameter provid
I started getting the following errors from my puppet master:
> Error: Could not retrieve catalog from remote server: Error 400 on
SERVER: Invalid parameter provider at /some/module/manifests/foo.pp
The module would vary, but the error was always the same. I started
googling, searching list
