This is a good idea and is worth exploring for sure. I'll try to think of what it would do, etc.. but I also hope others chime in with their thought process too about the topic in general or their ideas on how it could work too.
On Saturday, May 3, 2014 7:06:20 PM UTC-4, Michael DeHaan wrote: > > I think a good question here, rather than saying "eh, this sucks" would be > finding what sort of hypothethical ansible-galaxy subcommands (that don't > exist) that you would like to see. > > Knowing what these commands might be would be helpful in understanding > what could be optimized. > > Finally, once we decide on what they could be, we could entertain patches > around adding those subcommands to ansible-galaxy. > > This is better than creating *another* tool, outside of core, by all means > -- and keeps things simpler. > > > > On Sat, May 3, 2014 at 6:57 PM, Michael DeHaan > <[email protected]<javascript:> > > wrote: > >> Yeah, fortunately, you're missing the ansible-galaxy CLI, which is used >> to download things. >> >> Manual copying is not required. >> >> >> >> >> On Sat, May 3, 2014 at 2:27 PM, AntelopeSalad >> <[email protected]<javascript:> >> > wrote: >> >>> Here is a list of manual steps that you need to take such that you can >>> actively work on a playbook that requires a role that you've decided to >>> extract and put on the galaxy. >>> >>> Here is the work flow: >>> https://gist.github.com/AntelopeSalad/e55db863fd6b8bdf155c >>> >>> I've only been using ansible for a few days but even after doing this >>> workflow twice I already feel inclined to never make a public role again >>> because of how difficult it is to maintain while using it in a playbook >>> that you're actively developing. >>> >>> So I'm thinking it would be possible to make a python based or bash >>> command line app to make this less painful because I'm not sure it belongs >>> in the ansible-galaxy binary but maybe it does. I haven't really thought >>> about. >>> >>> Are there better work flows that I'm missing out which don't involve >>> custom tooling? >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Ansible Project" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to [email protected] <javascript:>. >>> To post to this group, send email to >>> [email protected]<javascript:> >>> . >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/ansible-project/ab43cc97-bc86-4e2a-a11d-37931635acbc%40googlegroups.com<https://groups.google.com/d/msgid/ansible-project/ab43cc97-bc86-4e2a-a11d-37931635acbc%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/b01fbcd3-8728-4333-b231-116199ca056f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
