From de85c11bd1e75accae387747de4687837a28e6c4 Mon Sep 17 00:00:00 2001 From: Felix Fontein Date: Mon, 4 Jan 2021 11:06:49 +0100 Subject: [PATCH] [stable-1] Add OC, hashi_vault and Google removal announcements (#1560) * Add removal announcements. * Remove Latin abbrevation. * Add hashi_vault removal announcement. --- changelogs/fragments/google-migration.yml | 10 ++++++++++ changelogs/fragments/hashi_vault-migration.yml | 9 +++++++++ changelogs/fragments/oc-migration.yml | 9 +++++++++ 3 files changed, 28 insertions(+) create mode 100644 changelogs/fragments/google-migration.yml create mode 100644 changelogs/fragments/hashi_vault-migration.yml create mode 100644 changelogs/fragments/oc-migration.yml diff --git a/changelogs/fragments/google-migration.yml b/changelogs/fragments/google-migration.yml new file mode 100644 index 0000000000..b555507ed7 --- /dev/null +++ b/changelogs/fragments/google-migration.yml @@ -0,0 +1,10 @@ +major_changes: +- | + For community.general 2.0.0, the Google modules will be moved to the `community.google `_ collection. + A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. + + If you use Ansible 2.9 and explicitly use Google modules from this collection, you will need to adjust your playbooks and roles to use FQCNs starting with ``community.google.`` instead of ``community.general.``, + for example replace ``community.general.gcpubsub`` in a task by ``community.google.gcpubsub``. + + If you use ansible-base and installed ``community.general`` manually and rely on the Google modules, you have to make sure to install the ``community.google`` collection as well. + If you are using FQCNs, for example ``community.general.gcpubsub`` instead of ``gcpubsub``, it will continue working, but we still recommend to adjust the FQCNs as well. diff --git a/changelogs/fragments/hashi_vault-migration.yml b/changelogs/fragments/hashi_vault-migration.yml new file mode 100644 index 0000000000..c78bfa7563 --- /dev/null +++ b/changelogs/fragments/hashi_vault-migration.yml @@ -0,0 +1,9 @@ +major_changes: +- | + For community.general 2.0.0, the hashi_vault lookup plugin will be moved to the `community.hashi_vault `_ collection. + A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. + + If you use Ansible 2.9 and explicitly use hashi_vault lookup plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.hashi_vault.hashi_vault`` instead of ``community.general.hashi_vault``. + + If you use ansible-base and installed ``community.general`` manually and rely on the hashi_vault lookup plugin, you have to make sure to install the ``community.hashi_vault`` collection as well. + If you are using FQCNs, in other words ``community.general.hashi_vault`` instead of ``hashi_vault``, it will continue working, but we still recommend to adjust this FQCN as well. diff --git a/changelogs/fragments/oc-migration.yml b/changelogs/fragments/oc-migration.yml new file mode 100644 index 0000000000..3e6850228f --- /dev/null +++ b/changelogs/fragments/oc-migration.yml @@ -0,0 +1,9 @@ +major_changes: +- | + For community.general 2.0.0, the OC connection plugin will be moved to the `community.okd `_ collection. + A redirection will be inserted so that users using ansible-base 2.10 or newer do not have to change anything. + + If you use Ansible 2.9 and explicitly use OC connection plugin from this collection, you will need to adjust your playbooks and roles to use FQCNs ``community.okd.oc`` instead of ``community.general.oc``. + + If you use ansible-base and installed ``community.general`` manually and rely on the OC connection plugin, you have to make sure to install the ``community.okd`` collection as well. + If you are using FQCNs, in other words ``community.general.oc`` instead of ``oc``, it will continue working, but we still recommend to adjust this FQCN as well.