- is not a valid attribute for a Play
When ever you get the above error firstly crosscheck that the ansible attribute you have mentioned is correct. If it is correct then the issue probably is that you have created tasks as follows:---
- vars_prompt:
- name: "var1"
prompt: "Please pass variable"
private: no
- fail: msg="var1 is not passed or blank"
when: var1 is undefined or ( var1 is defined and storeid == "" )
when it should be as follows:---
vars_prompt:
- name: "var1"
prompt: "Please pass variable"
private: no
tasks:
- fail: msg="var1 is not passed or blank"
when: var1 is undefined or ( var1 is defined and storeid == "" )
the example referenced is just a task. It is not a valid playbook because it is missings a hosts declaration and the module call is not under a tasks section. - ERROR! conflicting action statements: fail, command
I get this error if I have a task as follows:
- name: deploy
win_get_url:
url: 'http://server_ip/builds/build.zip'
dest: 'D:\build.zip'
win_unzip:
src: D:\build.zip
dest: D:\You cannot have multiple actions listed inside a single task like this. Instead you need to do this:- name: deploy get url
win_get_url:
url: 'http://server_ip/builds/build.zip'
dest: 'D:\build.zip'
- name: deploy unzip
win_unzip:
src: D:\build.zip
dest: D:\ - Ansible task to check API status
Here I am checking ES cluster health:
[code]
- name: Get ES cluster health
uri:
url: http://{{inventory_hostname}}:9200/_cluster/health
return_content: yes
register: cluster_status
- set_fact:
es_cluster_health: "{{ cluster_status.content | from_json }}"
- fail: msg="ES cluster not healthy"
when: "es_cluster_health.status != 'yellow'"
[/code]
You can compare the status with any string you want. Here I am comparing it with string "yellow"
First install and configure vault using this tutorial: https://apassionatechie.wordpress.com/2017/03/05/hashicorp-vault/ Use the latest version of vault. Then install salt using the steps given here: https://docs.saltstack.com/en/latest/topics/installation/ If you face any issues then refer these links: https://apassionatechie.wordpress.com/2017/07/31/salt-issues/ https://apassionatechie.wordpress.com/2017/08/03/salt-stack-formulas/ Now let's integrate vault and salt so that we can access vault secrets from inside salt state. First let's add some key values into our vault. vault write secret/ssh/user1 password="abc123" Then you can check it by reading: vault read secret/ssh/user1 To allow salt to access your secrets you must firstly create a policy as follows: salt-policy.hcl [code] path "secret/*" { capabilities = ["read", "list"] } path "auth/*" { capabilities = ["read", "list","sudo",...
Comments
Post a Comment