Support solo_legacy_mode

[hirose31]

Do you have plan to support solo_legacy_mode?

• knife solo takes --legacy-mode option and execute chef-solo with --legacy-mode option
• lib/knife-solo/resources/solo.rb.erb supports solo_legacy_mode and we puts solo_legacy_mode true into .chef/knife.rb

[matschaffer]

Oh, interesting idea. Just cut over to zero and have people use --legacy-mode if they need solo.

Not something that had occurred to me yet.

The biggest roadblock in my mind for zero right now is that (last time I checked) zero requires JSON roles & environments, not ruby.

I'd guess a lot of people using knife-solo are still using ruby roles & environments so I want to make sure there's some road forward without a full migration.

[matschaffer]

(fwiw, knife-solo doesn't get a whole lot of attention from me these days either, so there's that)

[hirose31]

Latest chef-solo loads DataBags via HTTP when solo_legacy_mode is false (default), so chef-solo invoked from knife-solo cannot load from data_bags/* in local filesystem...

• https://github.com/chef/chef/blob/master/lib/chef/data_bag.rb#L121-L143

I'm trying to migrate my Chef-12.0 + knife solo + Berksfile + the environment cookbook pattern system (I know it's legacy!) to using Chef-12.18 with minimal effort. But this issue blocks.

[matschaffer]

Oh, ouch. I didn't hear this news https://discourse.chef.io/t/chef-solo-will-be-local-mode-by-default/8499

(Guess you can tell how long I've been out of the chef-world ;) )

Now I see why you mention this.

I would be fine with a PR to provide a way to pass in the local mode flag into knife-solo->chef-solo as a workaround.

I could be implemented fairly simply I think.