feat(ansible): update community.sops ( 2.0.2 → 2.4.0 )

[parsec-renovate]

This PR contains the following updates:

Package	Type	Update	Change
community.sops	galaxy-collection	minor	2.0.2 → 2.4.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

ansible-collections/community.sops (community.sops)

v2.4.0

Compare Source

Release Summary

Feature release.

Minor Changes

• Support OpenSuSE Tumbleweed (and probably also Leap) in the community.sops.install role. Right now only Tumbleweed is tested in CI, so support for Leap has not been verified (#​299).

v2.3.0

Compare Source

Release Summary

Feature release.

The main new feature of this release is ansible-core 2.21 support for community.sops.load_vars. ansible-core 2.21 is the first version to explicitly allow action plugins to set variables, which finally allows community.sops.load_vars to set variables the same way as ansible.builtin.include_vars.

Minor Changes

• all modules and plugins - allow retrieving private age keys and private SSH keys through commands with the new age_key_cmd and age_ssh_private_key_cmd options (#​282, #​286).
• all modules and plugins - allow to configure GCP access with the gcp_oauth_access_token and gcp_kms_client_type options (#​282, #​286).
• load_vars - now supports ansible-core 2.21's way of actually loading variables, instead of returning ansible_facts. The behavior for this can be controlled through the new return_method option, which is by default set to auto. On ansible-core 2.21+, auto behaves the same as vars-only (return proper variables), and for ansible-core before 2.21 the same as facts-only (return ansible_facts) (#​283).
• sops_encrypt - support providing HuaweiCloud KMS key IDs with the huawei_cloud_kms option (#​282, #​286).

v2.2.7

Compare Source

Release Summary

Maintenance release.

Known Issues

• When using the community.sops.load_vars with ansible-core 2.20, note that the deprecation of INJECT_FACTS_AS_VARS causes deprecation warnings to be shown every time a variable loaded with community.sops.load_vars is used. This is due to ansible-core deprecating INJECT_FACTS_AS_VARS without providing an alternative for modules like community.sops.load_vars to use. If you do not like these deprecation warnings, you have to explicitly set INJECT_FACTS_AS_VARS to true. DO NOT change the use of SOPS encrypted variables to ansible_facts. The situation will hopefully improve in ansible-core 2.21 through the promised API that allows action plugins to set variables; community.sops will adapt to use it, which will make the warning go away. (The API was originally promised for ansible-core 2.20, but then delayed.)

v2.2.6

Compare Source

Release Summary

Bugfix and maintenance release.

Bugfixes

• Clean up plugin code that does not run on the target (#​275).
• Note that the MIT licenced code in plugins/module_utils/_six.py has been removed (#​275).
• sops vars plugin - ensure that loaded vars are evaluated also with ansible-core 2.19+ (#​273).

v2.2.5

Compare Source

Release Summary

Maintenance release.

Bugfixes

• load_vars action - avoid another deprecated module utils from ansible-core (#​270).
• load_vars action - avoid deprecated import from ansible-core that will be removed in ansible-core 2.21 (#​272).

---

Configuration

📅 Schedule: (in timezone America/New_York)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate.