Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request description
Description of the change
Following Yorc use of Ansible 2.10 to address issue (GH-648),
updated playbooks to remove deprecation warnings and fix what was already deprecated in previous versions and has been removed in Ansible 2.10
What I did
org/ystia/ansible/linux/ansible/playbooks/create.yml
python_requirements_facts
is nowpython_requirements_info
.paramiko was removed from Ansible requirements.txt and has now to be installed separately.
org/ystia/dns/dnsmasq/ansible/playbooks/roles/jriguera.dnsmasq/tasks/install.yml
Not anymore able to use Jinja tests as filters like
changed
ormatch
=> replace:
when: value|changed
bywhen: value is changed
org/ystia/experimental/consul/linux/ansible/playbooks/consul_configure.yaml
Jinja test
match
cannot be used anymore as filter.Parameter
subjectAltName
must be used inopensl_csr
, not inopenssl_certificate
org/ystia/experimental/consul/linux/ansible/playbooks/consul_connects_agent_to_server.yml
org/ystia/experimental/consul/linux/ansible/playbooks/consul_connects_servers_wan.yaml
Jinja test
match
cannot be used anymore as filter.org/ystia/experimental/consul/linux/ansible/playbooks/consul_install.yaml
python_requirements_facts
is nowpython_requirements_info
.Fixed a warning asking to define groups for a user.
org/ystia/experimental/consul/linux/ansible/playbooks/roles/jriguera.dnsmasq/tasks/install.yml
org/mongodb/linux/ansible/playbooks/roles/undergreen.ansible-role-mongodb/tasks/configure.yml
Jinja test
changed
cannot be used anymore as filter.org/ystia/slurm/ansible/playbooks/install-RedHat.yml
Invoking "yum" or apt only once while using a loop via squash_actions is deprecated
org/ystia/ssl/ansible-ssl-certificates/playbooks/configure.yml
Parameter
subjectAltName
must be used inopensl_csr
, not inopenssl_certificate
org/ystia/terraform/linux/ansible/playbooks/create.yml
Invoking "yum" or apt only once while using a loop via squash_actions is deprecated
org/ystia/yorc/alien4cloud-yorc-provider/playbook/connect_yorc.yml
Using here a dpeprecated feature relying on pyopenssl instead of cryptography, otherwise certficates generated were causing exceptions like this one:
org/ystia/yorc/alien4cloud-yorc-provider/playbook/create_orchestrator.yml
org/ystia/yorc/alien4cloud/playbook/create_orchestrator.yml
Ansible uri parameter HEADER_* is removed
=> replace
HEADER_cookie
andHEADER_Content-Type
by:org/ystia/yorc/yorc/linux/ansible/playbooks/configure.yml
Parameter
subjectAltName
must be used inopensl_csr
, not inopenssl_certificate
How to verify it
Changes are incorporated in yorc toca_types.zip in pull request ystia/yorc#686
and can be used performing a bootstrap of yorc.
Description for the changelog
Update Ansible to 2.10 (GH-136)
Applicable Issues
Fixes #136