GithubHelp home page GithubHelp logo

Comments (6)

majormoses avatar majormoses commented on July 17, 2024

@emilhdiaz first off thank you for looking into the issue and coming back with useful information about how to solve the problem. While I was hoping to target only chef 12.x when I wrote this I see that there are Netuitive users still using chef 11. This is creating a higher barrier of entry than I had hoped so I am willing to have some chef 11 backwards compatibility. That being said Chef 12.x will be officially supported and Chef 11.x will be best effort.

This particular issue seems like a very simple fix. If you could throw together a patch based off this commit: johnbellone/chef-vault-cookbook@d1d4930 I would be more than happy to review and merge it.

from chef-netuitive.

majormoses avatar majormoses commented on July 17, 2024

@emilhdiaz if you are ready could please include a test suite in your .kitchen.yml so I can start testing?

from chef-netuitive.

majormoses avatar majormoses commented on July 17, 2024

@emilhdiaz I was taking a look at the way the .kitchen.yml and the tests are set up here is what I am thinking how we should structure it:
I would mv test/integration/default/serverspec test/integration/helpers/serverspec/shared_spec.rb

In test/integration/chef12/serverspec have a simple include on the shared spec and do the same for chef11.

we then rename the default suite in .kitchen.yml to be something like chef12 and set require_chef_omnibus for each version we want to test.

Does this make sense? I am open to other options.

from chef-netuitive.

majormoses avatar majormoses commented on July 17, 2024

Just to make sure this is captured here: I have a branch with chef 11 compatibility: https://github.com/Netuitive/chef-netuitive/tree/feature/chef-11-compatibility

This issue is to allow chef 12 and 11 code to coexist peacefully...

from chef-netuitive.

majormoses avatar majormoses commented on July 17, 2024

@createor @shawnbutts I dont have access to make the chef 11 branch a protected branch, could you please do so to prevent accidental deletion?

from chef-netuitive.

majormoses avatar majormoses commented on July 17, 2024

@emilhdiaz as per: https://discourse.chef.io/t/chef-owned-community-cookbooks-now-require-chef-12-1-or-later/9435 I think that it would not make sense to put forth any further effort on chef 11. I would strongly encourage you to upgrade to a newer version of opsworks as they do support chef 12.

from chef-netuitive.

Related Issues (18)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.