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 WARNING on ansible.utils.unicode.to_str #11

Closed
fabriziopandini opened this issue Aug 15, 2017 · 4 comments
Closed

DEPRECATION WARNING on ansible.utils.unicode.to_str #11

fabriziopandini opened this issue Aug 15, 2017 · 4 comments

Comments

@fabriziopandini
Copy link
Owner

Running
$ vagrant-playbook -f cluster-setup.yaml

We got this message from ansible:
[DEPRECATION WARNING]: ansible.utils.unicode.to_str is deprecated. Use ansible.module_utils._text.to_native instead. This feature will be removed in version 2.4. Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.

@fabriziopandini
Copy link
Owner Author

According to https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/roadmap/ROADMAP_2_4.rst the 2.4 release of ansible targets Target: Mid-September 2017;

@fabriziopandini
Copy link
Owner Author

ansible.module_utils._text warns that This module_util is currently internal implementation. We want to evaluate this code for stability and API suitability before making backwards compatibility guarantees. The API may change between releases. Do not use this unless you are willing to port your module code. so it is not clear if this is stable or not. trying to reach out someone in the ansible team to get this sorted out

@fabriziopandini
Copy link
Owner Author

#rabin-io
I fixed this as well with the same approach of #12 (similar to vendoring in golang)
NB This is not yet the complete removal from ansible depencency, but it removes this annoyng message.

Version 0.7.5 is out !
Please let me know if I can close this issue as well

@rabin-io
Copy link
Contributor

rabin-io commented Nov 2, 2017

yep, seems to be resolved.

thanks again.

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