render: 11.0.0b1

rendered/11.0.0b1/awx.awx.md

@@ -0,0 +1,65 @@
+# Community package requirements: sanity tests and repository management
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `24.6.1` of `awx.awx`, corresponding to the `24.6.1` tag in this repo, fails one or more of the required sanity tests.
+
+The contents in the `24.6.1` git tag do not match `awx-awx-24.6.1.tar.gz` as uploaded to Ansible Galaxy. For future releases, please make sure that the contents uploaded to Galaxy match the sources that were tagged as that release. See the [Repository management requirements][repo-mgmt] for more information.
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+> **💡 NOTE:**
+>
+> Check the `[explain]` links below for more information about each test and how to fix failures.
+> See [Sanity Tests: Ignores](https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/ignores.html) in the dev guide if, after reading the test-specific documentation, you still believe an error is a false positive.
+
+The test `ansible-test sanity --test validate-modules` [[explain](https://docs.ansible.com/ansible-core/2.18/dev_guide/testing/sanity/validate-modules.html)] failed with 14 errors:
+
+``` text
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'applications' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credential_types' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'credentials' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'execution_environments' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'inventory_sources' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'notification_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'organizations' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'projects' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'schedules' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'teams' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'users' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+plugins/modules/export.py:0:0: nonexistent-parameter-documented: Argument 'workflow_job_templates' is listed in DOCUMENTATION.options, but not accepted by the module argument_spec
+```
+
+
+
+## File divergences
+
+The following files differ between the `24.6.1` git tag and `awx-awx-24.6.1.tar.gz` on Ansible Galaxy:
+
+- `plugins/module_utils/controller_api.py` (`WRONG_HASH`)
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/azure.azcollection.md

@@ -0,0 +1,45 @@
+# Community package requirements: sanity tests
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `3.0.0` of `azure.azcollection`, corresponding to the `v3.0.0` tag in this repo, fails one or more of the required sanity tests.
+
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+> **💡 NOTE:**
+>
+> Check the `[explain]` links below for more information about each test and how to fix failures.
+> See [Sanity Tests: Ignores](https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/ignores.html) in the dev guide if, after reading the test-specific documentation, you still believe an error is a false positive.
+
+The test `ansible-test sanity --test validate-modules` [[explain](https://docs.ansible.com/ansible-core/2.18/dev_guide/testing/sanity/validate-modules.html)] failed with 1 error:
+
+``` text
+plugins/modules/azure_rm_adapplication.py:0:0: collection-deprecated-version: Argument 'available_to_other_tenants' in argument_spec has a deprecated removed_in_version '3.0.0', i.e. the version is less than or equal to the current version of this collection (3.0.0)
+```
+
+
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/check_point.mgmt.md

@@ -0,0 +1,27 @@
+# Community package requirements: repository management
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+
+The contents in the `v6.2.1` git tag do not match `check_point-mgmt-6.2.1.tar.gz` as uploaded to Ansible Galaxy. For future releases, please make sure that the contents uploaded to Galaxy match the sources that were tagged as that release. See the [Repository management requirements][repo-mgmt] for more information.
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+
+## File divergences
+
+The following files differ between the `v6.2.1` git tag and `check_point-mgmt-6.2.1.tar.gz` on Ansible Galaxy:
+
+- `LICENSE` (`WRONG_HASH`)
+- `changelogs/.plugin-cache.yaml` (`WRONG_HASH`)
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/cisco.aci.md

@@ -0,0 +1,47 @@
+# Community package requirements: sanity tests
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `2.10.1` of `cisco.aci`, corresponding to the `v2.10.1` tag in this repo, fails one or more of the required sanity tests.
+
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+> **💡 NOTE:**
+>
+> Check the `[explain]` links below for more information about each test and how to fix failures.
+> See [Sanity Tests: Ignores](https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/ignores.html) in the dev guide if, after reading the test-specific documentation, you still believe an error is a false positive.
+
+The test `ansible-test sanity --test validate-modules` [[explain](https://docs.ansible.com/ansible-core/2.18/dev_guide/testing/sanity/validate-modules.html)] failed with 3 errors:
+
+``` text
+plugins/modules/aci_cloud_subnet.py:0:0: parameter-documented-aliases-differ: Argument 'address' in argument_spec has names 'address', but its documentation has names 'address', 'subnet'
+plugins/modules/aci_cloud_subnet.py:0:0: parameter-documented-aliases-differ: Argument 'name' in argument_spec has names 'name', 'subnet', but its documentation has names 'name'
+plugins/modules/aci_l3out_extsubnet.py:0:0: parameter-documented-aliases-differ: Argument 'extepg' in argument_spec has names 'extepg', 'extepg_name', 'name', but its documentation has names 'extepg', 'extepg_name'
+```
+
+
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/cisco.dnac.md

@@ -0,0 +1,49 @@
+# Community package requirements: sanity tests
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `6.22.0` of `cisco.dnac`, corresponding to the `v6.22.0` tag in this repo, fails one or more of the required sanity tests.
+
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+> **💡 NOTE:**
+>
+> Check the `[explain]` links below for more information about each test and how to fix failures.
+> See [Sanity Tests: Ignores](https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/ignores.html) in the dev guide if, after reading the test-specific documentation, you still believe an error is a false positive.
+
+The test `ansible-test sanity --test validate-modules` [[explain](https://docs.ansible.com/ansible-core/2.18/dev_guide/testing/sanity/validate-modules.html)] failed with 5 errors:
+
+``` text
+plugins/modules/discovery.py:0:0: option-equal-up-to-casing: Multiple options/aliases are equal up to casing: option 'snmpROCommunity', option 'snmpRoCommunity'
+plugins/modules/discovery.py:0:0: option-equal-up-to-casing: Multiple options/aliases are equal up to casing: option 'snmpROCommunityDesc', option 'snmpRoCommunityDesc'
+plugins/modules/discovery.py:0:0: option-equal-up-to-casing: Multiple options/aliases are equal up to casing: option 'snmpRWCommunity', option 'snmpRwCommunity'
+plugins/modules/discovery.py:0:0: option-equal-up-to-casing: Multiple options/aliases are equal up to casing: option 'snmpRWCommunityDesc', option 'snmpRwCommunityDesc'
+plugins/modules/discovery.py:0:0: option-equal-up-to-casing: Multiple options/aliases are equal up to casing: option 'timeOut', option 'timeout'
+```
+
+
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/cisco.meraki.md

@@ -0,0 +1,44 @@
+# Community package requirements: sanity tests
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `2.18.3` of `cisco.meraki`, corresponding to the `v2.18.3` tag in this repo, fails one or more of the required sanity tests.
+
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+`ansible-test sanity` succeeded, but some required tests were ignored.
+
+### Invalid test ignores
+
+`tests/sanity/ignore-2.18.txt` contain ignores that are forbidden by the [CI testing requirements][ci-testing]:
+
+``` text
+plugins/modules/meraki_mx_content_filtering.py validate-modules!skip
+```
+
+Please fix these issues and remove the ignore entries.
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst

rendered/11.0.0b1/cisco.mso.md

@@ -0,0 +1,49 @@
+# Community package requirements: sanity tests
+
+(Note: This issue was filed in a semi-automated fashion on behalf of the Ansible Community Steering Committee. Let me know if you see errors in this issue.)
+
+As per the [Ansible community package inclusion requirements][ci-testing], collections must pass `ansible-test sanity` tests. Version `2.9.0` of `cisco.mso`, corresponding to the `v2.9.0` tag in this repo, fails one or more of the required sanity tests.
+
+
+Please see the errors below and address them. If these issues aren't addressed within a reasonable time period, the collection may be subject to [removal from Ansible][removal].
+
+*Please fix the issues identified below and then create a new Galaxy release so the fixes are caught in the next round of automated testing.*
+
+Thank you for your efforts and for being part of the Ansible package! We appreciate it.
+
+---
+
+## Sanity tests
+
+The following tests were run using `ansible-test` version `2.18.0`:
+
+- ansible-doc
+- compile
+- validate-modules
+- yamllint
+
+Note that this is only a subset of the required sanity tests. Please make sure you run them in all in your CI.
+
+### Results
+
+> **💡 NOTE:**
+>
+> Check the `[explain]` links below for more information about each test and how to fix failures.
+> See [Sanity Tests: Ignores](https://docs.ansible.com/ansible/latest/dev_guide/testing/sanity/ignores.html) in the dev guide if, after reading the test-specific documentation, you still believe an error is a false positive.
+
+The test `ansible-test sanity --test validate-modules` [[explain](https://docs.ansible.com/ansible-core/2.18/dev_guide/testing/sanity/validate-modules.html)] failed with 5 errors:
+
+``` text
+plugins/modules/mso_schema_site.py:0:0: parameter-documented-aliases-differ: Argument 'site' in argument_spec has names 'name', 'site', but its documentation has names 'site'
+plugins/modules/mso_schema_site.py:0:0: parameter-documented-aliases-differ: Argument 'template' in argument_spec has names 'template', but its documentation has names 'name', 'template'
+plugins/modules/mso_schema_site_bd_l3out.py:0:0: parameter-documented-aliases-differ: Argument 'bd' in argument_spec has names 'bd', but its documentation has names 'bd', 'name'
+plugins/modules/mso_schema_site_bd_l3out.py:0:0: parameter-documented-aliases-differ: Argument 'l3out' in argument_spec has names 'l3out', 'name', but its documentation has names 'l3out'
+plugins/modules/mso_tenant_site.py:0:0: parameter-documented-aliases-differ: Argument 'tenant' in argument_spec has names 'name', 'tenant', but its documentation has names 'tenant'
+```
+
+
+
+
+[ci-testing]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#ci-testing
+[repo-mgmt]: https://docs.ansible.com/ansible/latest/community/collection_contributors/collection_requirements.html#repository-management
+[removal]: https://github.com/ansible-collections/overview/blob/main/removal_from_ansible.rst