ansible-role-elasticsearch/tasks/compatibility-variables.yml

---

# It is possible to set these are defaults with messy jinja templating one liners however:
# 1. That is really hard to read and debug
# 2. When running multiple plays with the same role the defaults are not re-evaluated. An example of this
# can be seen in our the https://github.com/elastic/ansible-elasticsearch/blob/master/test/integration/xpack.yml
# integration test and in the Multi Node server documentation examples https://github.com/elastic/ansible-elasticsearch/blob/master/test/integration/xpack.yml

- name: Set the defaults here otherwise they can't be overriden in the same play if the role is called twice
  set_fact:
    es_repo_name: "{{ es_major_version }}"
    es_package_name: "elasticsearch"
    es_other_package_name: "elasticsearch-oss"
    es_other_repo_name: "{{ 'oss-' + es_major_version }}"
    es_other_apt_url: "deb {{ es_repo_base }}/packages/{{ 'oss-' + es_major_version }}/apt stable main"

- name: Use the oss repo and package if xpack is not being used
  set_fact:
    es_repo_name: "{{ 'oss-' + es_major_version }}"
    es_other_repo_name: "{{ es_major_version }}"
    es_other_apt_url: "deb {{ es_repo_base }}/packages/{{ es_major_version }}/apt stable main"
    es_package_name: "elasticsearch-oss"
    es_other_package_name: "elasticsearch"
  when:
    - not es_enable_xpack
Abstract 6.3 changes into a separate task to reduce all of the jinja one liner complexity Set ES_PATH_CONF when installing so upgrading from 6.2 to 6.3 works as expected 2018-06-14 14:44:31 +02:00			`---`

			`# It is possible to set these are defaults with messy jinja templating one liners however:`
			`# 1. That is really hard to read and debug`
			`# 2. When running multiple plays with the same role the defaults are not re-evaluated. An example of this`
			`# can be seen in our the https://github.com/elastic/ansible-elasticsearch/blob/master/test/integration/xpack.yml`
			`# integration test and in the Multi Node server documentation examples https://github.com/elastic/ansible-elasticsearch/blob/master/test/integration/xpack.yml`

			`- name: Set the defaults here otherwise they can't be overriden in the same play if the role is called twice`
			`set_fact:`
			`es_repo_name: "{{ es_major_version }}"`
[7.x] add support for elasticsearch 7.x and remove support for 5.x (#558) - add support for elasticsearch 7.x - remove support for elasticsearch 5.x - update kitchen-ansible configuration (install ansible and jmespath dependencies using os repositories) - replace geoip plugin in tests as this one is now embeded in elasticsearch since 6.7.0 (cf. https://www.elastic.co/guide/en/elasticsearch/plugins/6.7/ingest-geoip.html) - update discovery configuration for 7.x (in ES 7.x, discovery.zen.ping.unicast.hosts is replaced by discovery.seed_hosts and transport.tcp.port is replaced by transport.port, also discovery.seed_hosts is disabled on master nodes to avoid "master_not_discovered_exception" error when creating templates in the same play) - update index template structure for 7.x - update security realms settings for 7.x (cf. https://www.elastic.co/guide/en/elasticsearch/reference/current/breaking-changes-7.0.html#include-realm-type-in-setting) 2019-05-09 09:06:02 +02:00			`es_package_name: "elasticsearch"`
Allow switching between oss and standard packages Before only going from the standard package to oss was supported. Now this works properly in both directions. 2018-12-27 16:42:14 +01:00			`es_other_package_name: "elasticsearch-oss"`
Remove the other Elasticsearch repo when switching versions 2018-12-31 17:28:37 +01:00			`es_other_repo_name: "{{ 'oss-' + es_major_version }}"`
Template out the base of repo URLs Some popular artifact caches (e.g. Artifactory) do not provide HTTP CONNECT endpoints and thus aren't supported by es_proxy_host and es_proxy_port. This patch templates out the scheme and authority components (i.e. "https://artifacts.elastic.co" ) of the apt and yum repo URLs to accommodate the use of such artifact caches. 2019-01-16 16:11:51 -05:00			`es_other_apt_url: "deb {{ es_repo_base }}/packages/{{ 'oss-' + es_major_version }}/apt stable main"`
Abstract 6.3 changes into a separate task to reduce all of the jinja one liner complexity Set ES_PATH_CONF when installing so upgrading from 6.2 to 6.3 works as expected 2018-06-14 14:44:31 +02:00
			`- name: Use the oss repo and package if xpack is not being used`
			`set_fact:`
			`es_repo_name: "{{ 'oss-' + es_major_version }}"`
Remove the other Elasticsearch repo when switching versions 2018-12-31 17:28:37 +01:00			`es_other_repo_name: "{{ es_major_version }}"`
Template out the base of repo URLs Some popular artifact caches (e.g. Artifactory) do not provide HTTP CONNECT endpoints and thus aren't supported by es_proxy_host and es_proxy_port. This patch templates out the scheme and authority components (i.e. "https://artifacts.elastic.co" ) of the apt and yum repo URLs to accommodate the use of such artifact caches. 2019-01-16 16:11:51 -05:00			`es_other_apt_url: "deb {{ es_repo_base }}/packages/{{ es_major_version }}/apt stable main"`
Abstract 6.3 changes into a separate task to reduce all of the jinja one liner complexity Set ES_PATH_CONF when installing so upgrading from 6.2 to 6.3 works as expected 2018-06-14 14:44:31 +02:00			`es_package_name: "elasticsearch-oss"`
Allow switching between oss and standard packages Before only going from the standard package to oss was supported. Now this works properly in both directions. 2018-12-27 16:42:14 +01:00			`es_other_package_name: "elasticsearch"`
Abstract 6.3 changes into a separate task to reduce all of the jinja one liner complexity Set ES_PATH_CONF when installing so upgrading from 6.2 to 6.3 works as expected 2018-06-14 14:44:31 +02:00			`when:`
			`- not es_enable_xpack`