Maxwell G comments

Results 215 comments of


                                            Maxwell G

[Tracker] Serious collection requirements violations that require version pinning

cyberark.pas is *again* violating this guideline (https://github.com/ansible-community/ansible-build-data/pull/235#issuecomment-1556293107). I filed https://github.com/cyberark/ansible-security-automation-collection/issues/58.

[Tracker] Serious collection requirements violations that require version pinning

> inspur.ispim 2.0.1 is not tagged in https://github.com/ispim/inspur.ispim https://github.com/ispim/inspur.ispim/issues/24

[Tracker] Serious collection requirements violations that require version pinning

- purestorage.flasharray 1.22.0 contains [Breaking Changes](https://github.com/Pure-Storage-Ansible/FlashArray-Collection/blob/master/CHANGELOG.rst#breaking-changes-porting-guide)

[Tracker] Serious collection requirements violations that require version pinning

https://github.com/Pure-Storage-Ansible/FlashArray-Collection/issues/500

[Tracker] Serious collection requirements violations that require version pinning

``` ERROR: found collection dependency errors! ERROR: cisco.ise 2.6.2 version_conflict: ansible.utils-3.0.0 but needs >=2.0.0,=2.0.0,=2.0.0,

[Tracker] Serious collection requirements violations that require version pinning

- cisco.meraki: https://github.com/meraki/dashboard-api-ansible/issues/38 - cisco.dnac: https://github.com/cisco-en-programmability/dnacenter-ansible/issues/133 - cisco.ise: https://github.com/CiscoISE/ansible-ise/issues/112

Add linting workflow with yamllint; fix linting issues

I would prefer to have a nox or tox or pre-commit configuration (whichever you prefer but perhaps a good idea to standardize on nox) to run yamllint. This would make...

Document the automated release process

I'll try to give it a look later today.

Rename included ibm.spectrum_virtualize to ibm.storage_virtualize

The maintainers can unarchive the old repository (Github lets you do that), complete step 4, and then archive it again if they so desire.

use tagged releases to pull core porting guides

I'd like to reconsider this now that the tagged releases are created automatically in ansible-documentation.