On May 28, 2010, at 4:46 AM, Daniel Pittman wrote:
Luke Kanies l...@puppetlabs.com writes:
External data (that is, data specified outside of Puppet manifests)
seems to
keep coming up.
If you forgive me banging my own drum, it isn't just /external/
data; access
to data that puppet knows,
On May 28, 2010, at 9:56 AM, Jonathan A. Booth wrote:
On 05/28/2010 05:00 AM, Luke Kanies wrote:
* Alessandro's presentation caused someone to point out to me
afterward that case statements of this ilk:
case $operatingsytem {
debian: { ... }
redhat: { ... }
}
make a module difficult to
On May 28, 2010, at 12:41 PM, donavan wrote:
[...]
I also don't like the idea of just relying on a function - I'd like a
class to be able to declare that it relies on external data, so that
users know what they can configure in their class.
Isn't this part of parameterized classes? Today I'd
Luke Kanies l...@puppetlabs.com writes:
On May 28, 2010, at 4:46 AM, Daniel Pittman wrote:
Luke Kanies l...@puppetlabs.com writes:
External data (that is, data specified outside of Puppet manifests) seems
to keep coming up.
If you forgive me banging my own drum, it isn't just /external/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've been following this thread with interest and I think that Donavan
is hitting upon something that I've also been wanting.
However, the way I was looking at it was as a set of atomic, optionally
blocking, semaphores in a set of parallel threads.
