internet/community.crypto
3
0
Fork 0
mirror of https://github.com/ansible-collections/community.crypto.git synced 2026-05-07 22:03:01 +00:00
Code Issues Packages Projects Releases Wiki Activity

Use fqcn for modules listed in M() and seealso. (#72)

Browse Source
This commit is contained in:
Toshio Kuratomi
2020-06-17 01:29:18 -07:00
committed by GitHub
parent ff17a341af
commit cc45650e82
19 changed files with 88 additions and 79 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
plugins/modules/x509_certificate_info.py
View File

@@ -20,12 +20,14 @@ description:
cryptography will be preferred as a backend over PyOpenSSL (unless the backend is forced with
C(select_crypto_backend)). Please note that the PyOpenSSL backend was deprecated in Ansible 2.9
and will be removed in Ansible 2.13.
- Note that this module was called C(openssl_certificate_info) when included directly in Ansible up to version 2.9.
When moved to the collection C(community.crypto), it was renamed to M(x509_certificate_info). From Ansible 2.10 on, it can
still be used by the old short name (or by C(ansible.builtin.openssl_certificate_info)), which redirects to
- Note that this module was called C(openssl_certificate_info) when included directly in Ansible
up to version 2.9. When moved to the collection C(community.crypto), it was renamed to
M(community.crypto.x509_certificate_info). From Ansible 2.10 on, it can still be used by the
old short name (or by C(ansible.builtin.openssl_certificate_info)), which redirects to
C(community.crypto.x509_certificate_info). When using FQCNs or when using the
L(collections,https://docs.ansible.com/ansible/latest/user_guide/collections_using.html#using-collections-in-a-playbook)
keyword, the new name M(x509_certificate_info) should be used to avoid a deprecation warning.
keyword, the new name M(community.crypto.x509_certificate_info) should be used to avoid
a deprecation warning.
requirements:
- PyOpenSSL >= 0.15 or cryptography >= 1.6
author:
@@ -70,7 +72,7 @@ notes:
- All timestamp values are provided in ASN.1 TIME format, i.e. following the C(YYYYMMDDHHMMSSZ) pattern.
They are all in UTC.
seealso:
- module: x509_certificate
- module: community.crypto.x509_certificate
'''
EXAMPLES = r'''