summaryrefslogtreecommitdiff
path: root/docs/reference/migration/migrate_5_0/packaging.asciidoc
diff options
context:
space:
mode:
Diffstat (limited to 'docs/reference/migration/migrate_5_0/packaging.asciidoc')
-rw-r--r--docs/reference/migration/migrate_5_0/packaging.asciidoc12
1 files changed, 12 insertions, 0 deletions
diff --git a/docs/reference/migration/migrate_5_0/packaging.asciidoc b/docs/reference/migration/migrate_5_0/packaging.asciidoc
index 5911b964b6..977e20a76b 100644
--- a/docs/reference/migration/migrate_5_0/packaging.asciidoc
+++ b/docs/reference/migration/migrate_5_0/packaging.asciidoc
@@ -43,3 +43,15 @@ Previously, the scripts used to start Elasticsearch and run plugin
commands only required a Bourne-compatible shell. Starting in
Elasticsearch 5.0.0, the bash shell is now required and `/bin/bash` is a
hard-dependency for the RPM and Debian packages.
+
+==== Environmental Settings
+
+Previously, Elasticsearch could be configured via environment variables
+in two ways: first by using the placeholder syntax
+`${env.ENV_VAR_NAME}` and the second by using the same syntax without
+the `env` prefix: `${ENV_VAR_NAME}`. The first method has been removed
+from Elasticsearch.
+
+Additionally, it was previously possible to set any setting in
+Elasticsearch via JVM system properties. This has been removed from
+Elasticsearch.