Thanks Sam and Felix. Unfortunately I'm still very lost. (Which means there's probably lots of other potential contributors who are lost too.)
> If you have the module in your collection path What's a collection path? Do you mean that iam_role.py needs to be in a directory within my OS $PATH variable? Or do you mean this: https://docs.ansible.com/ansible/latest/reference_appendices/config.html#collections-paths If the latter, which folder do I put in that path? https://github.com/ansible-collections/community.aws/tree/master/plugins/modules or https://github.com/ansible-collections/community.aws or a folder that contains the clone of https://github.com/ansible-collections/community.aws ? I tried a -m command and got: ERROR! this task 'community.aws/iam_role.py' has extra params, which is only allowed in the following modules: import_tasks, raw, ansible.windows. win_command, win_command, add_host, meta, include_role, command, include_vars, include, win_shell, import_role, ansible.windows.win_shell, shell, include_tasks, group_by, set_fact, script That's a very confusing error message. Definitely not what I'd expect to see if I put the wrong value in ANSIBLE_COLLECTIONS_PATH. I passed in an empty dict as my argument. So how does it have too many params? How long do you expect it will take a newcomer to start contributing under this new split repo setup? Is it supposed to take 20 minutes, 3 hours? What's a realistic timeframe you're aiming for? I've contributed to Ansible before, and I'm still struggling. It was a struggle before, and even more of a struggle now. The relevant documentation just seems spread over too many pages. I think someone who knows how this works should make a quick start guide, like this <https://github.com/ansible-collections/community.aws/issues/120#issuecomment-651715514>. Just 4 paragraphs and 4 code blocks of commands. Thanks, Matt On Tuesday, June 30, 2020 at 6:40:16 AM UTC+10, Sam Doran wrote: > > Matt, > > Hopefully the documentation provided by Felix answered some of your > questions. I'll try to add a little more clarity. > > Do I need to clone both the collection repo, and the main ansible/ansible > repo? > > > No, but with some short term caveats. > > If you are only interested in working on collection content, then there is > no need to clone the ansible/ansible repo or run the hacking setup script. > You only need to clone the collection repo and make sure it is in your > collection path. > > The caveat is that Ansible 2.9, the current released version, has basic > support for collections. This was improved greatly in 2.10, which has not > been released. > > Start by using the latest version of Ansible 2.9 rather than a source > checkout of ansible/ansible. If you run into any issues, try using 2.10 > which you can install via pip. > > pip uninstall ansible && pip install ansible --pre > > If you want to run the ansible source as well as the collection source, > you certainly can do that (that's how I work). But it is not required to > use a source checkout of ansible/ansible in order to develop collections. > > > What is the new process for testing changes to the modules that have moved > to a collection? > > If I want to run my code locally > <https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#exercising-module-code-locally> > what > do I pass as the -m argument? What folder do I need to be in? > > > If you have the module in your collection path, you can test the module > using its fully qualified collection name (FQCN). For example, if you > module is located at: > > > ~/.ansible/collection/ansible_collections/matt/my_collection/plugins/modules/my_module.py > > You can run this module with this command: > > ansible all -m matt.my_collection.my_module -a '[args]' > > What about unit tests > <https://docs.ansible.com/ansible/latest/dev_guide/developing_modules_general.html#unit-tests>. > > Is the command the same? What folder do I need to be in? > > How do I run integration tests? The new AWS collection repo does not > have the policy file listed in the docs. > > > Per the docs > <https://docs.ansible.com/ansible/devel/dev_guide/developing_collections.html#testing-collections>, > > unit and integration tests must be run from the root directory of the > collection. The command is the same. > > Regarding the AWS test questions, I am not sure about the policy file. It > would be best to ask in #ansible-aws on Freenode IRC > > > --- > > Respectfully, > > Sam Doran > -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/90583cf1-7cf7-4214-aca6-50ad57a4f024o%40googlegroups.com.
