This PR adds a runtime.yml file and also updates the galaxy.yml file.
The runtime file is used by ansible at runtime to read through the collection to confirm if the user is running a version that matches the collections scope. This is now a required file as we move forward with certification as we will use it to display the versions you all support via the Automation Hub UI. A word on the specific version selected. The version 2.9.10 is when the final collection bits were merged into ansible and thus they became fully supported so that is why I selected that version, especially since you all were pilot partners of collections, this would be a correct version.
The update to the galaxy file just bumps the version for you.
As for next steps. I ran the sanity suite (the testing suite that gates certification) locally and your collection needs some updates. I will include steps on how to run the sanity suite below. As of the release of ansible-core version 2.11, you all will need to support python 3.8 so the commands below test directly on python 3. 8 but note that py 3.8 must be present in the environment or else the command will error. You can get the latest version of ansible-core from pip or you can use the latest version of ansible. Ansible-test is packaged with both ansible-core and ansible so if you have either installed, it is present.
steps to test:
navigate to the top level of the collection
ansible-test sanity --python 3.8
evaluate output and make changes
A lot of these tests are just enforcing python specific ansible things (like headers and formatting etc) but it will do some opionated linting and also a validation of modules.
This PR adds a runtime.yml file and also updates the galaxy.yml file.
The runtime file is used by ansible at runtime to read through the collection to confirm if the user is running a version that matches the collections scope. This is now a required file as we move forward with certification as we will use it to display the versions you all support via the Automation Hub UI. A word on the specific version selected. The version 2.9.10 is when the final collection bits were merged into ansible and thus they became fully supported so that is why I selected that version, especially since you all were pilot partners of collections, this would be a correct version.
The update to the galaxy file just bumps the version for you.
As for next steps. I ran the sanity suite (the testing suite that gates certification) locally and your collection needs some updates. I will include steps on how to run the sanity suite below. As of the release of
ansible-coreversion 2.11, you all will need to support python 3.8 so the commands below test directly on python 3. 8 but note that py 3.8 must be present in the environment or else the command will error. You can get the latest version of ansible-core from pip or you can use the latest version of ansible. Ansible-test is packaged with both ansible-core and ansible so if you have either installed, it is present.steps to test:
A lot of these tests are just enforcing python specific ansible things (like headers and formatting etc) but it will do some opionated linting and also a validation of modules.
Let me know if you have any question etc.