Simple and flexible tool for managing secrets
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Bugfix release.
yaml
when the file extension .yml
is used. Now both .yaml
and .yml
files use the SOPS --output-type=yaml
formatting (https://github.com/ansible-collections/community.sops/issues/164).Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Make fully compatible with and test against sops 3.8.0.
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Make compatible with and test against sops 1.8.0-rc.1.
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Maintenance/bugfix release for the move of sops to the new getsops GitHub organization.
sops_github_latest_detection=latest-release
, which broke due to sops moving to another GitHub organization (https://github.com/ansible-collections/community.sops/pull/151).Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Maintenance release with updated documentation.
From this version on, community.sops is using the new Ansible semantic markup <https://docs.ansible.com/ansible/devel/dev_guide/developing_modules_documenting.html#semantic-markup-within-module-documentation>
__
in its documentation. If you look at documentation with the ansible-doc CLI tool
from ansible-core before 2.15, please note that it does not render the markup
correctly. You should be still able to read it in most cases, but you need
ansible-core 2.15 or later to see it as it is intended. Alternatively you can
look at the devel docsite <https://docs.ansible.com/ansible/devel/collections/community/sops/>
__
for the rendered HTML version of the documentation of the latest release.
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Maintenance release.
pkg_mgr
fact is definitely available when installing on localhost
. This can improve error messages in some cases (https://github.com/ansible-collections/community.sops/issues/145, https://github.com/ansible-collections/community.sops/pull/146).Maintenance release.
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Feature release improving the installation role.
sops_github_latest_detection
option that allows to configure which method to use for detecting the latest release on GitHub. By default (auto
) first tries to retrieve a list of recent releases using the API, and if that fails due to rate limiting, tries to obtain the latest GitHub release from a semi-documented URL (https://github.com/ansible-collections/community.sops/pull/133).sops_github_token
option to allow passing a GitHub token. This can for example be used to avoid rate limits when using the role in GitHub Actions (https://github.com/ansible-collections/community.sops/pull/132).Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Feature release.
Full CHANGELOG: https://github.com/ansible-collections/community.sops/blob/main/CHANGELOG.rst
Maintenance release to improve compatibility with future ansible-core releases.