Skip to content

Commit

Permalink
Newer changelog fragment format.
Browse files Browse the repository at this point in the history
  • Loading branch information
geerlingguy committed Dec 1, 2020
1 parent d7829bc commit 59dfecb
Show file tree
Hide file tree
Showing 2 changed files with 14 additions and 2 deletions.
2 changes: 0 additions & 2 deletions changelogs/fragments/866-oc-move-to-okd.yaml

This file was deleted.

14 changes: 14 additions & 0 deletions changelogs/fragments/oc-migration-removal.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
removed_features:
- |
The ``oc`` connection plugin has been removed from this collection.
It has been migrated to the `community.okd <https://galaxy.ansible.com/community/okd>`_ collection.
If you use ansible-base 2.10 or newer, redirections have been provided.
If you use Ansible 2.9 and installed this collection, you need to adjust the FQCNs (``community.general.oc`` → ``community.okd.oc``) and make sure to install the community.okd collection.
breaking_changes:
- |
If you use Ansible 2.9 and the ``oc`` connection plugin from this collections, community.general 2.0.0 results in errors when trying to use the oc content by FQCN, like ``community.general.oc``.
Since Ansible 2.9 is not able to use redirections, you will have to adjust your playbooks and roles manually to use the new FQCNs (``community.okd.oc`` for the previous example) and to make sure that you have ``community.okd`` installed.
If you use ansible-base 2.10 or newer and did not install Ansible 3.0.0, but installed (and/or upgraded) community.general manually, you need to make sure to also install ``community.okd`` if you are using the ``oc`` plugin.
While ansible-base 2.10 or newer can use the redirects that community.general 2.0.0 adds, the collection they point to (community.okd) must be installed for them to work.

0 comments on commit 59dfecb

Please sign in to comment.