Hi,

bumping an old thread with a some news: I've built a proof-of-concept
implementation of John's constraint scheme. Enjoy:
https://github.com/ffrank/puppet/tree/constraints

I'd be grateful for any feedback. Constraints can currently be added as
normal resources to a manifest as shown in the README.

Each is limited to targetting a single resource. I'd be interested in
amending this so that metaparameter-like declarations such as

  resource => Package[foo,bar]
  resource => [ Package[foo], Service[bar] ]

are supported. There's also some TODOs such as tight validation (i.e.
syntax checks).

An idea for extending the concept is "weak" constrains that won't fail
if a targeted resource is not part of a catalog.

A PR is pending once these additions are complete.

Thanks in advance to anyone who takes a closer look.

Cheers,
Felix

On 02/20/2014 10:17 AM, Daniele Sluijters wrote:
> I like a constrains style solution much better myself to, wasn't aware
> of it at the time.
>
> I think with Puppet 4 we could introduce some additional pain, semver
> wise we'd be
> allowed to do that. If that helped fix this issue once and for all I'm
> pretty sure the
> community would support it too.

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-dev/534C6A4B.8020408%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.

Reply via email to