Comments (9)
I'm happy with this. Basically the main breakages aren't even in Chef syntax, but in the standard library.
from chef-netuitive.
Given that currently chef does not support < 14.x
anymore I think we should drop it: https://docs.chef.io/versions.html#end-of-life-eol-products. This cookbook was originally written in chef 12 days and ported limited functionality back to chef 11. We have continued to support both chef 12 and 13 for a very long time and its time we break compatibility. However we can do it in a way that allows continued development and maintenance on legacy code with purely community contributions.
In order to allow people to continue to use this cookbook regardless of the limitations within their orgs we are going to make some changes regarding legacy versions of this cookbook. Previously chef 11 support existed in feature/chef-11-compatibility
branch, I think using chef-client/$MAJOR
or something along those lines to indicate when we no longer aim to maintain compatibility with a version of chef-client
. Releases on github and supermarket will only be made from master which should reflect the latest version of chef that is supported. All other versions must be pulled from github branches. This is in part to avoid conflicts with versioning as we follow semver and do not want to tie our hands or make our versions confusing to users.
This would result in the creation of:
chef-client/11.x
: no longer supportedchef-client/12.x
: no longer supportedchef-client/13.x
: no longer supported
The master branch will be geared toward chef 14 until it is no longer supported, will be bumped to 15, etc.
Let me know what you think.
from chef-netuitive.
@ziggythehamster @rclagett could you two weigh in here?
from chef-netuitive.
This makes a lot of sense to me, and I'm on board with it. I like the idea of backwards compatibility branches for folks using the cookbook who haven't yet updated chef. Than you so much for the dedication @majormoses!
from chef-netuitive.
@rclagett it looks like I dont have enough access to make the chef-client/*
branches protected can you please enable those protections?
EDIT: once that has been done and #65 is merged and released this can be closed.
from chef-netuitive.
@majormoses I increased your access level. Could you give it another try?
from chef-netuitive.
@rclagett that worked for me, thank you.
https://github.com/Netuitive/chef-netuitive/settings/branch_protection_rules/5738962
For right now I enabled the basic protections and used a pattern to ensure that newly created branches following that pattern will auto be protected.
from chef-netuitive.
@majormoses This is great! Really appreciate you setting it all up.
from chef-netuitive.
released: https://supermarket.chef.io/cookbooks/netuitive/versions/1.0.0
from chef-netuitive.
Related Issues (18)
- Add support for epel based systems HOT 9
- Fix travis badge to go to the right repo
- switch travis ci test
- We should have a more feature full template HOT 29
- We should have some basic unit testing HOT 2
- bad metadata
- Need to specify cookbook name in template in
- netuitive-agent is not restarted when a custom collector is added or changed HOT 1
- Support language agents
- Backward compatibility for Chef 11 HOT 6
- Document Chef Requirements
- Typo: use_epl_repos should be use_epel_repos HOT 2
- [CI] Need to have integration tests run on prs automatically on travis HOT 2
- Support for chef client 12.16
- Integrate travis-ci to push to supermarket on git tag HOT 18
- Add Windows Support HOT 2
- Moderate severity security vulnerability detected in rack HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from chef-netuitive.