chore: use semantic-release cross-formula standard structure

[myii]

• Automated using ssf-formula (v0.1.0-rc.1)

[daks]

Looks good to me, I merge.

Waiting for more information (and the code! :) about this ssf-formula which looks like the right tool to easily propagate changes.
Are modifications on kitchen.yml completely automated? It seems to me that it can easily break.

[myii]

@daks Thanks for the merge.

Waiting for more information (and the code! :) about this ssf-formula which looks like the right tool to easily propagate changes.

I'll be putting it up for scrutiny soon and I welcome all feedback and collaboration on it. Because it also involves git operations and preparing the GitHub PRs via. the API (via. user-customisable scripts at the moment), I'm just working out the final parts as we get these first PRs merged (how to clear-up after merges, ready for the next batch of changes).

Are modifications on kitchen.yml completely automated? It seems to me that it can easily break.

kitchen.yml was the biggest challenge. I'll explain more when there's actual code to discuss. In a very general sense, I started by generating a very ugly template at the beginning (Jinja blocks everywhere!), capturing how all of the formulas were using the file. Then it was a fairly simple job of finding the common structure that would work in all cases. At the current time, that will mean a little more duplication (under each suite if there are multiple suites) but it provides a guaranteed structure that can be depended upon. The template is much simpler to work with, with nearly all of the data coming via. the map. I'm confident that it will suit our use-cases with new formulas as well.

[saltstack-formulas-travis]

🎉 This PR is included in version 0.4.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀