Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • v2.28.0
  • v2.27.0
  • v2.25.1
  • v2.24.3
  • v2.26.0
  • v2.24.2
  • v2.25.0
  • v2.24.1
  • v2.22.2
  • v2.23.3
  • v2.24.0
  • v2.23.2
  • v2.23.1
  • v2.23.0
  • v2.22.1
  • v2.22.0
  • v2.21.0
  • v2.20.0
  • v2.19.1
  • v2.18.2
21 results

ansible.cfg

Blame
    • Kenichi Omichi's avatar
      024a3ee5
      Replace callback_whitelist with callbacks_enabled (#8759) · 024a3ee5
      Kenichi Omichi authored
      When running molecule jobs, we saw the folloing warning message:
      
       [DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names
       to new standard, use callbacks_enabled instead. This feature will be removed
       from ansible-core in version 2.15. Deprecation warnings can be disabled by
       setting deprecation_warnings=False in ansible.cfg.
      
      callbacks_enabled has been added since Ansible 2.11 and Kubespray is using
      Ansible 2.12 at master branch. So we can use callbacks_enabled safely to
      avoid the warning message.
      024a3ee5
      History
      Replace callback_whitelist with callbacks_enabled (#8759)
      Kenichi Omichi authored
      When running molecule jobs, we saw the folloing warning message:
      
       [DEPRECATION WARNING]: [defaults]callback_whitelist option, normalizing names
       to new standard, use callbacks_enabled instead. This feature will be removed
       from ansible-core in version 2.15. Deprecation warnings can be disabled by
       setting deprecation_warnings=False in ansible.cfg.
      
      callbacks_enabled has been added since Ansible 2.11 and Kubespray is using
      Ansible 2.12 at master branch. So we can use callbacks_enabled safely to
      avoid the warning message.