Hi,
I’m hoping to give my role-lines default path values, on a per role basis. I’m trying to create a imperative-based repository for roles, and I think the ability to build a long path to every role in a simple way is absolutely key.
That bit about imperative means: I hope to decompose states back into package-manager like quasi-commands, before optionally reassembling imperative-named roles into a declarative again, perhaps on a node-wide role level. This probably sounds like gibberish. What I want is a package manager-like experience when applying Ansible roles from a community-vetted repository that is multi-distro from the ground up, because declarative is great, but so is imperative, when you know you want finer telemetry. The “Origin” option deomstrated below gives room for something like: this software comes from sourcecode on github, not EPEL. Configuration by exception.
I would have approached this from a tags perspective, but I think we established that all tags in a play will run by default, if calling from a playbook, without a programmatic exception.
Anyway, here’s the project I created on GitHub to resolve the lack of an Ansible Roles Repository; it’s called Plethorole.
You may want to look over the readme to get a better idea where I’m going with all this.
side note: All methods (imperatives and otherwise) are to be kept idempotent by policy unless absolutely necessary.
Now, I’d like to get away from: