* refactor(elasticsearch-setup-job): create-indices.sh readability
The script contains many copy-pasting and is not easy to follow.
Add comments, extract commonly used operations into functions, unify approaches.
* fix(elasticsearch-setup-job): AWS indices creation
Fix the issue where Amazon OpenSearch (AWS ES) indices are incorrectly initialised
and the Analytics screen shows errors only.
* feat(elasticsearch-setup-job): configuration hint
mention USE_AWS_ELASTICSEARCH env value if it seems it's set the wrong way
* fix(elasticsearch-setup-job): silent curl
* fix(elasticsearch-setup-job): better USE_AWS_ELASTICSEARCH hint
* docs(elasticsearch-setup-job): index dropping explained
- more comments
- more defensive approach
- index file renamed
* fix(elasticsearch-setup-job): script fixes
* merge(elasticsearch-setup-job): merging in PR #5937
* merge(elasticsearch-setup-job): merging in PR #5963
* merge(elasticsearch-setup-job): merging in PR #5975
Co-authored-by: Pedro Silva <pedro@acryl.io>
Merges in changes from our ES7 branch, and drops support for ES5.
This is a breaking change due to the upgrade, we have a ES5 branch at the commit before this.
These tests verify that, given an index settings and mappings, data can be written to the index, and read from it with a query_all query. These are very simple sanity tests.
We can, and should, write more complex tests that specific to each index in the future.