Hello,
I've never looked at heira before. I'm looking into upgrading from 2.7 to
3, and it seems that heira is the recommended way to do things now. From
what I've read so far, it looks like one professed reason to use it is to
go from parameterized classes to hiera overrides, because I guess
On May 4, 2013, at 9:50 PM, Josh wrote:
> So instead of:
>
> class bar ($foo = 'blah') { ... }
>
> One would have something like:
>
> class bar { $foo = heira('bar::foo', 'blah') }
>
> Is that correct?
That's the hard way to do it. The easy way is to do
class bar ($foo) { … }
and H
On Sat, May 4, 2013 at 9:50 PM, Josh wrote:
>
> I'm not yet sold on heira; so far it seems to just shift complexity
> outside of the classes and add a little more in the process, with
> hierarchies and stuff, and now I have data in multiple places... I still
> need case statements to handle diffe
Hi Josh,
Here's what we found. I would love to hear about other approaches because
we're still debating and building out our service.
1. Yes it's a great way to escape from parameterized classes. If you ever
needed to 'include' a class in two places, parameterized classes makes this
difficult
Hi Larry,
I'm curious to your opinion on point # 3, are you talking about OS packages
or your organizations app version? If the latter, I was thinking of using
hiera, maybe with a backend other than yaml such as redis, to store the
version of the app, that way like you said it could be used in
Thanks for the replies!
While I don't like the idea of "reaching in" to a class to set its
variables, given the design flaws in Puppet with parameterized classes, I
agree that this is a strength of Heira (so far, the only one, IMHO). Maybe
this irks me because I'm also a developer who started with
On Sunday, May 5, 2013 8:43:52 PM UTC-5, Josh wrote:
>
> Thanks for the replies!
>
Although it's a bit tardy, I'd like to add a word or two here.
First, I think it's a mischaracterization to say "heira is the recommended
way to do things now." Certainly, hiera is the favored interface with
> > I'm curious to your opinion on point # 3, are you talking about OS
> packages or your organizations app version? If the latter, I was thinking
> of using hiera, maybe with a backend other than yaml such as redis, to
> store the version of the app, that way like you said it could be used in
