Release 2.0.0-a1.

This commit is contained in:
Felix Fontein 2021-07-31 11:16:14 +02:00
parent 42babbe50f
commit bd113788ef
4 changed files with 28 additions and 9 deletions

View file

@ -5,6 +5,19 @@ Community RouterOS Release Notes
.. contents:: Topics
v2.0.0-a1
=========
Release Summary
---------------
First prerelease for a new major release with a breaking change in the behavior of ``community.routeros.api``.
Breaking Changes / Porting Guide
--------------------------------
- api - due to a programming error, the module never failed on errors. This has now been fixed. If you are relying on the module not failing in case of idempotent commands (resulting in errors like ``failure: already have such address``), you need to adjust your roles/playbooks. We suggest to use ``failed_when`` to accept failure in specific circumstances, for example ``failed_when: "'failure: already have ' in result.msg[0]"`` (https://github.com/ansible-collections/community.routeros/pull/39).
v1.2.0
======

View file

@ -81,3 +81,18 @@ releases:
- 37-api-validate-cert-options.yml
- ansible-core-_text.yml
release_date: '2021-06-29'
2.0.0-a1:
changes:
breaking_changes:
- 'api - due to a programming error, the module never failed on errors. This
has now been fixed. If you are relying on the module not failing in case of
idempotent commands (resulting in errors like ``failure: already have such
address``), you need to adjust your roles/playbooks. We suggest to use ``failed_when``
to accept failure in specific circumstances, for example ``failed_when: "''failure:
already have '' in result.msg[0]"`` (https://github.com/ansible-collections/community.routeros/pull/39).'
release_summary: First prerelease for a new major release with a breaking change
in the behavior of ``community.routeros.api``.
fragments:
- 2.0.0-a1.yml
- 39-api-fail.yml
release_date: '2021-07-31'

View file

@ -1 +0,0 @@
release_summary: First prerelease for a new major release with a breaking change in the behavior of ``community.routeros.api``.

View file

@ -1,8 +0,0 @@
breaking_changes:
- >-
api - due to a programming error, the module never failed on errors. This has now been fixed.
If you are relying on the module not failing in case of idempotent commands
(resulting in errors like ``failure: already have such address``), you need to adjust your roles/playbooks.
We suggest to use ``failed_when`` to accept failure in specific circumstances,
for example ``failed_when: "'failure: already have ' in result.msg[0]"``
(https://github.com/ansible-collections/community.routeros/pull/39).