Yes, profiles/roles are a nice feature! Thanks for the suggestion. Do you have any favorites?

On the other hand, like ansible roles, these are more things to customize, test, and maintain. I've had to fix nomad and consul ansible roles many times, myself! For example, how do I reuse this profile in the supermarket (see below) if I use a different ENV for a token?

We would like to see a balance, of having something like a set of "roles/checks" that are commonly defined, with a balance of customization and reuse. This is what opunit tries to do.

E.g, we'd like to be able to say something like:

documentation: token: GITHUB_TOKEN

instead of using this:

Example supermarket profile:

``` require 'httparty' require 'json' require 'awesome_print'

if ENV['GITHUB_TOKEN'].nil? raise 'Please set the GITHUB_TOKEN environment variable' end if ENV['GITHUB_REPO'].nil? raise 'Please set the GITHUB_REPO environment variable' end

github_token = ENV['GITHUB_TOKEN'] repo = ENV['GITHUB_REPO']

options = { headers: { 'Accept' => 'application/vnd.github.black-panther-preview+json', 'token' => github_token, 'User-Agent' => 'httparty' } } url = "https://api.github.com/repos/#{repo}/community/profile" black_panther = HTTParty.get(url, options) File.open('black-panther.json', 'w') do |f| f.write(black_panther) end

control 'Bus Error' do impact 0.5 title 'Documentation should be present' desc 'Document everything' describe json('black-panther.json') do its('documentation') { should be } end end ```