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

Port Playbooks to Ansible 2.0 #11

Closed
oguya opened this issue Feb 29, 2016 · 2 comments
Closed

Port Playbooks to Ansible 2.0 #11

oguya opened this issue Feb 29, 2016 · 2 comments

Comments

@oguya
Copy link
Owner

oguya commented Feb 29, 2016

There are couple of warnings that I've received when running these playbooks using ansible 2.0.

  • Use synchronize module rather than rsync

    TASK [solr : Copy solr.xml config. files] **************************************
    changed: [localhost]
    [WARNING]: Consider using synchronize module rather than running rsync
    
  • Remove bare variables—e.g. solr_cores—use full variable syntax instead—e.g. '{{solr_cores}}'

    TASK [solr : Create Solr core data dir] ****************************************
    [DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks
    so that the environment value uses the full variable syntax ('{{solr_cores}}').
    This feature will be removed in a future release. Deprecation warnings can be 
    disabled by setting deprecation_warnings=False in ansible.cfg.
    changed: [localhost] => (item=ckan_default)
    

Have a look at Ansible 2.0 porting guide

@oguya
Copy link
Owner Author

oguya commented Mar 2, 2016

A few warnings I've received so far using by running these playbooks on ansible 2.0:

TASK [solr : Copy solr.xml config. files] **************************************
changed: [ckan01]
 [WARNING]: Consider using synchronize module rather than running rsync

TASK [solr : Create Solr core data dir] ****************************************
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{solr_cores}}'). This feature will be removed in a future release. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
changed: [ckan01] => (item=ckan_default)

TASK [solr : Create Solr core conf dir] ****************************************
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{solr_cores}}'). This feature will be removed in a future release. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
changed: [ckan01] => (item=ckan_default)

TASK [solr : Populate Solr core conf dir] **************************************
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{solr_cores}}'). This feature will be removed in a future release. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
changed: [ckan01] => (item=ckan_default)

TASK [solr : Create core.properties placeholder] *******************************
[DEPRECATION WARNING]: Using bare variables is deprecated. Update your playbooks so that the environment value uses the full variable syntax ('{{solr_cores}}'). This feature will be removed in a future release. 
Deprecation warnings can be disabled by setting deprecation_warnings=False in ansible.cfg.
changed: [ckan01] => (item=ckan_default)

oguya added a commit that referenced this issue Mar 2, 2016
Using bare variables—e.g. solr_cores—is deprecated from ansible 2.0
onwards. Therefore, we should use the full variable syntax e.g. "{{ solr_cores }}"

This commit is related to issue #11 on GitHub[2].

1. #11

Signed-off-by: James Oguya <oguyajames@gmail.com>
@oguya
Copy link
Owner Author

oguya commented Mar 11, 2016

Apart from bare variables & sudo/sudo_user, I don't see any other changes to make.

@oguya oguya closed this as completed Mar 11, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant