Perhaps some of the scan/report stuff might be interesting.
I'm more interesting in seeing support for non-github git repos (git:// and
ssh://) and a possibly some refinements in versioning role downloads (some
people ask about multiple versions of roles and workflow, and things like
cook-libraria
I try to set sane defaults. Almost all of my playbooks look like:
- name: Do something
hosts: some_group
sudo: true
roles:
- { role: my.role, tags: }
I have about 15 roles that work with that identical setup minus the name.
What changes between them are a few inventory variables.
So
On Tue, Jul 22, 2014 at 6:47 PM, Nick Janetakis
wrote:
> Unclear of how inventory and example playbooks are related.
>>
>
> In a lot of cases the playbook itself is always the same except for the
> name of the role. I have around 20 roles on the galaxy and pretty much all
> of them have an identi
>
> Unclear of how inventory and example playbooks are related.
>
In a lot of cases the playbook itself is always the same except for the
name of the role. I have around 20 roles on the galaxy and pretty much all
of them have an identical playbook in the example.
The thing that changes is over
On Tue, Jul 22, 2014 at 10:06 AM, Nick Janetakis
wrote:
> Also I may point out it appears you are using a new templating system :)
>>
>
> I'm not. I'm using jinja2 and the tool itself has no extra dependencies
> other than what ansible requires. The %foo syntax is only used on the
> command line
>
> Also I may point out it appears you are using a new templating system :)
>
I'm not. I'm using jinja2 and the tool itself has no extra dependencies
other than what ansible requires. The %foo syntax is only used on the
command line so you as the scripter have access to the current role name i
On Tue, Jul 22, 2014 at 9:09 AM, Michael DeHaan wrote:
>
>
>
> On Tue, Jul 22, 2014 at 8:56 AM, Nick Janetakis
> wrote:
>
>> Thanks for the feedback, I'll try to address some of your concerns:
>>
>> *Re: "run":*
>> The stemmed from the ginas project. It's currently 50 roles inside of a
>> single
On Tue, Jul 22, 2014 at 8:56 AM, Nick Janetakis
wrote:
> Thanks for the feedback, I'll try to address some of your concerns:
>
> *Re: "run":*
> The stemmed from the ginas project. It's currently 50 roles inside of a
> single git repo. The author of ginas recently decided he's going to try and
> b
Thanks for the feedback, I'll try to address some of your concerns:
*Re: "run":*
The stemmed from the ginas project. It's currently 50 roles inside of a
single git repo. The author of ginas recently decided he's going to try and
break up each role into stand alone git repos and release whatever
No offense intended, I saw this on twitter yesterday, and honestly, I
didn't get it.
First off, ansible-galaxy is already a command line tool help manage
(create, stub out, and download ansible roles). ansible-galaxy is already
open source as a command line tool, and it's not galaxy specific (jus
What do you guys think about https://github.com/nickjj/ansigenome. I
released it yesterday and would appreciate some feedback.
Here's a snippet from the readme:
Ansigenome is a command line tool designed to help you manage your Ansible
roles. It does 6 things:
>
>
> *scan* a path containing Ans
11 matches
Mail list logo
