Stop using master

[lukehinds]

This role (unlike the role with master) is positioned for deploying Keylime into eventual production type environments. Thus it should be using releases and not building from master. We need a var in place, to allow users to pin to a specific release.

[dawud]

Using 'requirements.yml` allows to define "a tag value, commit hash, or branch name" to specify where to pull content from.
Moreover, Galaxy "imports any git tags matching the Semantic Version format as versions. In turn, a specific version of a role can be downloaded by specifying one of the imported tags".

If the intention is to provide this content to be consumed from Galaxy, I'd suggest tagging commits is a valid mechanism. Coupled with using feature branches for development activities.

[lukehinds]

Sounds good to me @dawud , thank you for the input. Would you like to work on this / shall I assign to you?

[dawud]

Sure, thanks.

[lukehinds]

Thanks are all mine. If when you're happy, feel free to get something set up on galaxy or poke me to do it!