Even += works in order to append values he he.
May be that recipes attr definitions just override attr files ones.
Mike: I have checked out that arrays merge works well on defaults attr files + defaults on role. So environment and roles examples on the link, are just examples, i think.
Can a opscode dev, explain what is the exactly behaviour with arrays on attributes? Looks like it depends where you define the attr override works as expected o_O
My experience with this issue was similar, however I found that << doesn't play nice with the autovivification.Consequently I've been using this pattern as a workaround:
node.default['foo'] = node['foo'].to_a.push('bar')Regards,
LukeOn 21 October 2013 16:04, Michael Glenney < " target="_blank"> > wrote:
I don't have a complete answer but I know that:1) The doc you linked to specifically calls out roles and environments. Might be a clue2) When writing a provider for a cookbook attributes are mutable. So maybe this will work for you within a recipe:node.default['foo'] << 'bar'Sent from my iPhoneSo what exactly node.default['x'] = value do on recipes? Looks like a direct override... O_oWorks as expected, and results on node['foo'] = ['littlebar','bar']default_attributes (:foo => ['bar'])Defining on a role:Is overrided by the one i defined on the recipe, resulting node['foo'] = ['bar']node.default['foo'] = ['littlebar']The one that i have already on defaults.rb attribute file:node.default['foo'] = ['bar']Array attributes are merged, i have checked out that this is the behaviour when using default attributes on attribute files and roles.But when i try to define a default attribute on one recipe:
--
Si necesitas una máquina para hacer algo y no la compras al final te darás cuenta de que has pagado lo mismo y no tienes la máquina.--Henry FordAlberto
Archive powered by MHonArc 2.6.16.