Ansible Contributor Summit

We are happy to announce that the registration for the Ansible Contributor Summit is open!

Why

• This is a great opportunity for interested people to meet, discuss related topics, share their stories and opinions, get the latest important updates and just to hang out together.

• There will be different announcements & presentations by Community, Core, Cloud, Network, and other teams.

• Current contributors will be happy to share their stories and experience with newcomers.

• There will be links to interactive self-passed instruqt scenarios shared during the event that help newcomers learn different aspects of development.

Where/when

Online on Matrix and Youtube. Tuesday, April 12, 2022, 12:00 - 20:00 UTC.

How to join

• Add the event to your calendar. Use the ical URL (for example, in Google Calendar "Add other calendars" > "Import from URL") instead of importing the .ics file so that any updates to the event will be reflected in your calendar.

• Check out the Summit page:

  • Add you name to attendees.
  • Suggest summit topics that would be interesting to you to hear about.
  • Vote on and propose changes to topics suggested by others.
  • If you want to be a presenter, please contact the Ansible Community team via [email protected].

We are looking forward to seeing you!:)

Summary

Hi! As part of the ansible community package release process, we've determined that version 21.10.1 of netapp.azure was released to Ansible Galaxy but not properly tagged in this Git repository. This violates the repository management section of the Collection Requirements:

Every collection MUST have a public git repository. Releases of the collection MUST be tagged in said repository. This means that releases MUST be git taged and that the tag name MUST exactly match the Galaxy version number. Tag names MAY have a v prefix, but a collection's tag names MUST have a consistent format from release to release.

Additionally, collection artifacts released to Galaxy MUST be built from the sources that are tagged in the collection's git repository as that release. Any changes made during the build process MUST be clearly documented so the collection artifact can be reproduced.

If the collection maintainers do not respond to this issue within a reasonable a amount of time, the collection is subject to Removal from ansible.

Component Name

collection

Ansible Version

all

Azure NetApp Files Collection Version

latest

Playbook

irrelevant

Steps to Reproduce

irrelevant

Expected Results

irrelevant

Actual Results

irrelevant

SUMMARY

Dear maintainers,

This is important for your collections!

• In accordance with the Community decision, we have created the news-for-maintainers repository for announcements of changes impacting collection maintainers (see the examples) instead of Issue 45 that will be closed soon.

  • To keep yourself well-informed and, therefore, things in your collection working, please subscribe to the repository by using the Watch button in the upper right corner on the repository's home page.
  • If you do not want to get notifications about related discussions, please subscribe only to Issues.
  • Please read the brief guidelines on how the repository should be used.
  • Please avoid unnecessary discussions in issues, use the Discussions feature. Every comment posted will notify a lot of folks!

• Also we would like to remind you about the Bullhorn contributor newsletter which has recently started to be released weekly. To learn what it looks like, see the past releases. Please subscribe and talk to the Community via Bullhorn!

• Join us in #ansible-social (for news reporting & chat), #ansible-community (for discussing collection & maintainer topics), and other channels on Matrix/IRC.

• Help the Community and the Steering Committee to make right decisions by taking part in discussing and voting on the Community Topics that impact the whole project and the collections in particular. Your opinion there will be much appreciated!

Thank you!

Dear maintainers,

According to the Collection requirements, collections included in the ansible package MUST run the ansible-test sanity command from the latest stable ansible-core branch.

It has been recently announced via the news-for-maintainers repository that the ansible-core stable-2.13 branch is available for testing.

• Please add the stable-2.13 branch to your test matrix in the .github/workflows directory, at least, in the sanity jobs section. Any questions, just mention me here.

• If you have integration and/or unit tests, please consider adding the branch to the corresponding sections too.

• If you're not subscribed to the news-for-maintainers repository, please do it to avoid CI related issues in the future.

• If the issue is not relevant to your collection, please close it.

Thank you!

Based on the community decision to use true/false for boolean values in documentation and examples, we ask that you evaluate booleans in this collection and consider changing any that do not use true/false (lowercase).

See documentation block format for more info (specifically, option defaults).

If you have already implemented this or decide not to, feel free to close this issue.

P.S. This is auto-generated issue, please raise any concerns here

(Note: This issue was filed in a semi-automated fashion. Let me know if you see errors in this issue.)

As per the Ansible community package inclusion requirements, collections must pass ansible-test sanity tests. Version 21.10.1 of netapp.azure, corresponding to the 21.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.

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.16.1:

• 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 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] failed with 16 errors:

plugins/modules/azure_rm_netapp_account.py:0:0: parameter-type-not-in-doc: Argument 'thumbprint' in argument_spec defines type as 'str' but documentation doesn't define type
plugins/modules/azure_rm_netapp_account.py:0:0: parameter-type-not-in-doc: Argument 'x509_certificate_path' in argument_spec defines type as 'path' but documentation doesn't define type
plugins/modules/azure_rm_netapp_account.py:0:0: undocumented-parameter: Argument 'thumbprint' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_account.py:0:0: undocumented-parameter: Argument 'x509_certificate_path' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_capacity_pool.py:0:0: parameter-type-not-in-doc: Argument 'thumbprint' in argument_spec defines type as 'str' but documentation doesn't define type
plugins/modules/azure_rm_netapp_capacity_pool.py:0:0: parameter-type-not-in-doc: Argument 'x509_certificate_path' in argument_spec defines type as 'path' but documentation doesn't define type
plugins/modules/azure_rm_netapp_capacity_pool.py:0:0: undocumented-parameter: Argument 'thumbprint' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_capacity_pool.py:0:0: undocumented-parameter: Argument 'x509_certificate_path' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_snapshot.py:0:0: parameter-type-not-in-doc: Argument 'thumbprint' in argument_spec defines type as 'str' but documentation doesn't define type
plugins/modules/azure_rm_netapp_snapshot.py:0:0: parameter-type-not-in-doc: Argument 'x509_certificate_path' in argument_spec defines type as 'path' but documentation doesn't define type
plugins/modules/azure_rm_netapp_snapshot.py:0:0: undocumented-parameter: Argument 'thumbprint' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_snapshot.py:0:0: undocumented-parameter: Argument 'x509_certificate_path' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_volume.py:0:0: parameter-type-not-in-doc: Argument 'thumbprint' in argument_spec defines type as 'str' but documentation doesn't define type
plugins/modules/azure_rm_netapp_volume.py:0:0: parameter-type-not-in-doc: Argument 'x509_certificate_path' in argument_spec defines type as 'path' but documentation doesn't define type
plugins/modules/azure_rm_netapp_volume.py:0:0: undocumented-parameter: Argument 'thumbprint' is listed in the argument_spec, but not documented in the module documentation
plugins/modules/azure_rm_netapp_volume.py:0:0: undocumented-parameter: Argument 'x509_certificate_path' is listed in the argument_spec, but not documented in the module documentation

Summary

It looks like this collection is effectively unmaintained. According to the current community guidelines for collections, we will consider removing it in a future version of the Ansible community package. Please see Unmaintained collection: netapp.azure for more information.

At least one month after this announcement appears here and on Bullhorn, the Ansible Community Steering Committee will vote on whether this collection is considered unmaintained and will be removed, or whether it will be kept. If it will be removed, this will happen earliest in Ansible 10. Please note that people can still manually install the collection with ansible-galaxy collection install netapp.azure even when it has been removed from Ansible.

Component Name

Irrelevant, this collection looks unmaintained.

Ansible Version

Irrelevant, this collection looks unmaintained.

Azure NetApp Files Collection Version

Irrelevant, this collection looks unmaintained.

Playbook

Irrelevant, this collection looks unmaintained.

Steps to Reproduce

Irrelevant, this collection looks unmaintained.

Expected Results

Irrelevant, this collection looks unmaintained.

Actual Results

Irrelevant, this collection looks unmaintained.