I love this addition.
Continuing from our conversation on Twitter, I can offer a few suggestions
and comments:
- As mentioned, the ability to have multiple roles in just 1 repo would
make contributing and maintaining roles much simpler.
- Scaffolding is nice, but if we already have a functional role, then it
becomes unnecessary. I think the most important is to ensure the meta file
exists, and the proper directory structure is in place
(rolename/{tasks,meta,vars,files}) etc. Perhaps a cli addition to verify
the a role's dir/structure prior to uploading it?
- In regards to versioning, I like the idea of placing the version number
in the meta file. What if you tracked/map the meta file/version changes
with the git commit SHA? Then you can provide a download URL like
this:
https://github.com/aw/ansible-galaxy-vagrant/archive/fbd110c5fb42281971955a1c654af1c8ae261278.zip
Just some thoughts. In any case, great effort!
<3
AW
On Thursday, December 19, 2013 7:07:06 PM UTC, Michael DeHaan wrote:
>
>
> A quick update:
>
> For those that are uploading roles, note that you need to edit the
> meta/main.yml generated by the CLI to remove the "or higher" in the Ansible
> version for the upload to be accepted.
> This is already fixed on the development branch of Ansible and we'll be
> updating Ansible 1.4.2 shortly to include the updated CLI. (That will
> also understand your ansible.cfg roles_path).
>
> Things look very very stable -- Various other improvements to Galaxy
> itself will role out later in the beta period.
>
> Thanks all!
>
--
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].
For more options, visit https://groups.google.com/groups/opt_out.
