Changes impacting Collection Contributors and maintainers

[gundalow]

NO LONGER IN USE

Please subscribe to ansible-collections/news-for-maintainers

Details of what's changed

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 this issue.

• 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!

[gundalow]

Remove tests/sanity/requirements.txt from collections

The file tests/sanity/requirements.txt was put into collections by mistake, it should be removed.

See #43 for details

[gundalow]

Update collection tests from RHEL 7.6 to 7.8

Update CI to run against RHEL 7.8/

See #44 for details

[gundalow]

Changelog process for collections

Feedback needed

We have a continuing need for changelogs (or release notes) to cover:

• ansible/ansible - currently has a working solution using changelog fragments
• collections - two options mentioned so far are reno and towncrier
• Ansible Community Distribution (ACD) - a bundled package that includes the trimmed down ansible/ansible and a set of curated collections that will mimic the current user experience of Ansible with all batteries included (2.9 level of content). ACD has no proposed solution yet, but whatever is used by collections has to provide fragments that can be drawn up into an ACD changelog/release note.

There are various proposals outlined #18 Please comment and vote for preferred solution.

[relrod]

Update collection tests from RHEL 8.1 to 8.2

Update CI to run against RHEL 8.2.

See #54 for details.

[samccann]

Remove ANSIBLE_METADATA

Use meta/routing.yml for deprecated and removed status.

Do collection owners want a DOCUMENTATION field to cover preview vs stable status for a module??

See #57 for details.

[gundalow]

ansible-test (validate-modules) now checks for correct module deprecation

All, we've just merged ansible/ansible#68646
This means that deprecated modules and plugins

• MUST NOT have a leading _
• Deprecations are defined by meta/routing.yml (see community.general for an example)

Call to action

• Please do a CI run and if anything fails please update as per Tidyup deprecations community.general#195

[relrod]

Update collection tests to test on Fedora 32

Update CI to run against Fedora 32.

See #59 for details.

[gundalow]

Dropping ANSIBLE_METADATA

In Ansible 2.9 and earlier we had the concept of ANSIBLE_METADATA, to express support level and deprecation. With the move to Collections, and support being defined if a Collection is in Galaxy vs Automation Hub, ANSIBLE_METADATA is no longer needed.See #57 for background

Call to action

• Please bulk remove the ANSIBLE_METADATA section from all modules in your collection and reference this issue in the PR so we can track what's been done.

• community.general Remove ANSIBLE_METADATA community.general#339
• community.network Remove ANSIBLE_METADATA community.network#35
• community.aws Remove METADATA and cleanup galaxy.yml community.aws#70?
• your collection...

[felixfontein]

Sanity tests for removed_in_version and deprecated_aliases

The devel version of ansible-test now validates removed_in_version and deprecated_aliases (ansible/ansible#66920). For collections, these are assumed to be collection version numbers, i.e. in semver format. Version numbers not in that format - for example verison numbers taken from ansible/ansible during the migration - are not valid semver versions and thus fail validation.

Call to action

• Please ensure that deprecation version numbers are valid collection version numbers.
• Alternatively, if you do not have a deprecation / versioning plan yet (and thus no idea how to rewrite Ansible versions to collection versions), temporarily update tests/sanity/ignore-2.10.txt as in Ignore invalid deprecation version numbers community.general#337.

• community.general
• community.network
• community.aws
• ansible....
• partner1....