Reid,
Ultimately, I went with your original suggestion ... it made more sense
to build an 'rs_tag::conditional' definition that does the logic. Its done
and implemented, thanks for the idea!
Matt Wise
Sr. Systems Architect
Nextdoor.com
On Fri, May 23, 2014 at 11:31 AM, Reid Vandewiele wrote:
In the type for it to make sense and be consistent with the usual semantics
I think you'd have to make it some kind of valid ensurable state. For
example, let people specify ensure=present_if_in_rightscale or some better
state name.
That also suggests to options like ensure=$is_rightscale or other
Thats definitely one way to do it... and in fact, I may do that today if I
can't come up with another solution. I'd prefer to do it in the actual
provider, but I could see how this is arguably cleaner. Before I do that
though, is there no clean way to do this inside the Type or Provider?
Matt Wise
How about just create a utility define to go with your custom type? E.g. create
an rs_tag::conditional define, then use that instead of the rs_tag type
directly. You can put the conditional logic in the define and it's about as
clean as it gets. You also don't have to muck about with the logic a
