>
> Not practical? Come on, it's one line of code:
>
> `find /`.split(/\n/)
>
>
I started running that command on my VM a few minutes ago, and I'm still
waiting for it to return.
Unfortunately, the RAL resource find function is implemented like this:
res = type(request).instances.find { |o| o.name ==
resource_name(request) }
res ||= type(request).new(:name => resource_name(request), :audit =>
type(request).properties.collect { |s| s.name })
Which means we have pessimized resource lookups. I suspect that's a bug.
Does anyone know why we're doing it that way? (Apparently I cut and paste
that behavior from the XMLRPC version into the Indirector version without
asking the question)
Ah, here we are: real 6m17.871s
And that's without even md5ing the contents!
Basically (and joking aside) I don't like having a dead spot in a language
> based on "oh but you couldn't possibly want that" reasoning.
We've long said that you can't model an entire system state using puppet
resources - that most of it is unmanaged, and only few things are explicitly
managed. Listing all files on a system seems uncomfortably close to trying
to capture the entire machine state to me.
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
