Fix linting in Ansible playbooks related with Elastic
This commit is contained in:
parent
2efe6e6268
commit
61d05a0cdd
@ -1,5 +1,5 @@
|
||||
---
|
||||
- hosts: <YOUR_ELASTICSEARCH_IP>
|
||||
roles:
|
||||
- role: /etc/ansible/roles/wazuh-ansible/roles/elastic-stack/ansible-elasticsearch
|
||||
- role: /etc/ansible/roles/wazuh-ansible/roles/elastic-stack/ansible-elasticsearch
|
||||
elasticsearch_network_host: '<YOUR_ELASTICSEARCH_IP>'
|
||||
|
||||
@ -6,7 +6,7 @@
|
||||
elasticsearch_network_host: <node-1 IP>
|
||||
node_name: node-1
|
||||
elasticsearch_bootstrap_node: true
|
||||
elasticsearch_cluster_nodes:
|
||||
elasticsearch_cluster_nodes:
|
||||
- <node-1 IP>
|
||||
- <node-2 IP>
|
||||
- <node-3 IP>
|
||||
@ -22,7 +22,7 @@
|
||||
vars:
|
||||
instances:
|
||||
node1:
|
||||
name: node-1 # Important: must be equal to elasticsearch_node_name.
|
||||
name: node-1 # Important: must be equal to elasticsearch_node_name.
|
||||
ip: <node-1 IP> # When unzipping, the node will search for its node name folder to get the cert.
|
||||
node2:
|
||||
name: node-2
|
||||
@ -43,10 +43,10 @@
|
||||
- <node-1 IP>
|
||||
- <node-2 IP>
|
||||
- <node-3 IP>
|
||||
|
||||
|
||||
- hosts: <node-3 IP>
|
||||
roles:
|
||||
- role: /etc/ansible/roles/wazuh-ansible/roles/elastic-stack/ansible-elasticsearch
|
||||
- role: /etc/ansible/roles/wazuh-ansible/roles/elastic-stack/ansible-elasticsearch
|
||||
elasticsearch_network_host: <node-3 IP>
|
||||
elasticsearch_node_name: node-3
|
||||
single_node: false
|
||||
|
||||
@ -5,4 +5,4 @@
|
||||
- role: ../roles/wazuh/ansible-filebeat
|
||||
filebeat_output_elasticsearch_hosts: localhost:9200
|
||||
- {role: ../roles/elastic-stack/ansible-elasticsearch, elasticsearch_network_host: '0.0.0.0', single_node: true}
|
||||
- { role: ../roles/elastic-stack/ansible-kibana, elasticsearch_network_host: 'localhost', elasticsearch_reachable_host: 'localhost' }s
|
||||
- { role: ../roles/elastic-stack/ansible-kibana, elasticsearch_network_host: 'localhost', elasticsearch_reachable_host: 'localhost' }
|
||||
Loading…
Reference in New Issue
Block a user