Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deprecation warnings: evaluating [] as a bare variable #60

Closed
tmtron opened this issue Aug 7, 2019 · 2 comments
Closed

deprecation warnings: evaluating [] as a bare variable #60

tmtron opened this issue Aug 7, 2019 · 2 comments

Comments

@tmtron
Copy link

tmtron commented Aug 7, 2019

sorry for my newbie question, but I am not sure, if I can change my config to get rid of these warnings, or if these warnings are okay for now and need to be fixed in this role.

in my playbook I try to deactivate the default cron job like this:

  vars:
    docker__cron_jobs: []

then I get this warning:

TASK [nickjj.docker : Configure Docker daemon environment variables] ***************************************************
[DEPRECATION WARNING]: evaluating [] as a bare variable, this behaviour will go away and you might need to add |bool to
 the expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle.. This feature will be removed in
version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

There is also another warning like this, which seems not related to my config:

TASK [nickjj.docker : Configure Docker daemon options (flags)] *********************************************************
[DEPRECATION WARNING]: evaluating [u'-H unix://'] as a bare variable, this behaviour will go away and you might need to
 add |bool to the expression in the future. Also see CONDITIONAL_BARE_VARS configuration toggle.. This feature will be
removed in version 2.12. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
@nickjj
Copy link
Owner

nickjj commented Aug 7, 2019

Hi,

Those are fixed on the master branch. I suppose it's about time I make a new release.

Edit: I just pushed v1.9.0 to the Galaxy which has these fixes and more.

@tmtron
Copy link
Author

tmtron commented Aug 7, 2019

thanks for the fast feedback and new release.
I've already upgraded to v1.9.0 and can confirm that the warnings are gone.

@tmtron tmtron closed this as completed Aug 7, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants