Configuration Management for IT Systems (CMITS) 1.3 has been released on GitHub
at https://github.com/afseo/cmits. From the README:
This is a toolset that makes it easier for network administrators to configure
IT systems in compliance with U.S. Department of Defense requirements, and to
err: Could not retrieve catalog from remote server: Error 400 on SERVER:
cannot generate tempfile
`/var/lib/puppet/yaml/facts/vagrant1.localdomain.yaml20131009-16545-8oie
5i-9'
warning: Not using cache on failed catalog
err: Could not retrieve catalog; skipping run
Security
The only gotcha I've found are a couple of versions of Puppet (2.7.20+
and 3.0.x) which don't load custom types from lib/ in the module, so
there's a workaround in the above file.
This seemingly innocuous statement has cleared up for me the problem of
being unable to require, from my custom
For those inside the US Department of Defense, the DoD Puppet project on
Software.forge.mil https://software.forge.mil/sf/projects/dodpuppet
has seen some activity recently.
(I apologize for posting a link to a site that most of those on the
puppet-users list can't access, but this is the place
I'm having scads of fun with custom resource types. But mine are getting
complicated enough that not having automated tests for them is starting
to seem really foolish. But the latest things I've seen about that issue
are from three years ago (https://github.com/mikepea/puppet-git,
With Puppet 2.7.20, it seems that when I write
file { '/tmp/bla':
owner = ['root', 'jared']
}
then if the owner of /tmp/bla is either root or jared, nothing happens,
and if not, the owner is changed to root. More generically speaking, my
reading of the code suggests that if the
This behavior when I provide multiple values for owner is just what I
want! But I don't want to depend on it if it might go away. Does
anyone
else use the owner and group properties this way? Is there
documentation
for this behavior that I've missed?
Ah. From
I encountered this issue yesterday when trying to reproduce another
issue. I discovered that you need to be using activerecord 3.0.11.
Later versions don't seem to work (error with a stack too deep) and
earlier versions don't seem to work (error with uninitialized
constant
ActiveRecord).
