Closed pooranpatel2512 closed 9 years ago
That attribute produces the following line inside of riak.conf
via the cuttlefish.rb
library:
riak_control.auth.mode = off
Can you share more about what you're trying to do? Are you attempting to create a riak-yetu
wrapper cookbook for Riak?
That’s correct. I suppose we could just try leaving this attribute out of our attribute declarations, as we aren’t changing the value.
Still, I’m puzzled by “string not matched” message.
On Nov 6, 2014, at 2:53 AM, Hector Castro notifications@github.com wrote:
That attribute produces the following line inside of riak.conf via the cuttlefish.rb library:
riak_control.auth.mode = off Can you share more about what you're trying to do? Are you attempting to create a riak-yetu wrapper cookbook for Riak?
— Reply to this email directly or view it on GitHub https://github.com/basho/riak-chef-cookbook/issues/158#issuecomment-61915610.
Something appears to be wrong with how you are accessing the nested hash. It is difficult for me to troubleshoot without a bit more of the context around your wrapper cookbook, but I would try dumping earlier levels of the hash to see if anything interesting is revealed:
Something like:
p default['riak']['config']['riak_control']
p default['riak']['config']['riak_control']['auth']
p default['riak']['config']['riak_control']['auth']['mode']
I wonder if a different type is somehow getting assigned to one of these, breaking the ability to nest hashes.
This hasn't been moved in a bit - if you are still experiencing issues I'd love to know but I haven't been able to replicate.
I'd say close it for now. If we find that we can predictably reproduce we can re-open.
We think the attribute
node['riak']['config']['riak_control']['auth']['mode']
is not used. Is this an expected behaviour?@bixu