Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • R rbfsmi-ansible
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • rbfsmi.imt
  • rbfsmi-ansible
  • Issues
  • #8
Closed
Open
Issue created Feb 13, 2021 by Dennis Baurichter@dennisbaContributor

hash_behaviour = merge is deprecated

Currently ansible.cfg sets hash_behaviour = merge, but that's deprecated and will be removed in Ansible 2.13:

$ ansible-config dump --only-changed
[DEPRECATION WARNING]: DEFAULT_HASH_BEHAVIOUR option, this feature is fragile and not portable, leading to 
continual confusion and misuse, use the ``combine`` filter explicitly instead. This feature will be removed 
from ansible-base in version 2.13. Deprecation warnings can be disabled by setting deprecation_warnings=False 
in ansible.cfg.
[...]

We should check where this merge behaviour is currently used and solve it without hash_behaviour = merge before Ansible 2.13.

Ansible release dates for time estimation:

  • 2.5: 2018-03-22
  • 2.6: 2018-06-28
  • 2.7: 2018-10-03
  • 2.8: 2019-05-16
  • 2.9: 2019-10-31
  • 2.10: 2020-08-13
  • 2.11: ?
  • 2.12: ?
  • 2.13: ?
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking