Querying is awesome, particularly with the new relationship syntax, and as a
more comprehensible alternative to class inheritance.
Package <| |>
The part I find frustrating is that it also *realizes* all the virtual
resources that match the query.
It would be immensely useful in my opinion if you could collect without
realizing. How could we get there?
Proposal here is that Package <| |> would realize, but Package <| |> { }
wouldn't.
Luke from a previous conversation:
I'm thinking that a collection with no {} on it should default to realizing
> resources but could throw a warning, and a collection with a {} on it should
> not realize. We would probably also want to make a collection a valid
> rvalue, and have it resolve to an array of resources in that case. This
> would probably cause some ordering issues, because collections are run many
> times, but functions are only called once.
Proposal here is that we add the ability to filter based upon whether
resources have been realized or not:
Me from a previous conversation:
Could we add the ability to query whether a given resource has
> been realized or not? How much of an ordering problem is this?
> Package <| state == virtual |>
> Package <| state == real |>
I'd like to keep this thread on this particular topic. In the course of
discussing this somewhere else we covered areas such as filtering on
provider where providers weren't explicitly set in the manifests, issues
around the defined() function, etc. Lets start new threads if we want to
discuss those peripheral issues.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
