* Add timezone support to Cron objects
* Add timezone support to CronnableSchedule
* XContent change to support parsing and display of TimeZone fields on schedules
* Case insensitive timezone parsing
* Doc changes
* YAML REST tests
* Equals, toString and HashCode now include timezone
* Additional random testing for DST transitions
* Migrate Cron class to use wrapped LocalDateTime
The algorithm depends on some quirks of calendar but LocalDateTime
correctly ignores DST during calculations so this uses a LocalDateTime
with a wrapper to emulate some of Calendar's behaviours that the Cron
algorithm depends on
* Additional documentation to explain discontinuity event behaviour
* Remove redundant conversions from ZoneId to TimeZone following move to LocalDateTime
* Add documentation warning that manual clock changes will cause unpredictable watch execution
* Update docs/reference/watcher/trigger/schedule.asciidoc
---------
Co-authored-by: Lee Hinman <dakrone@users.noreply.github.com>
* Update settings endpoint modified
Now accepts index.routing.allocation.* settings but denies changing
the allocation setting that keeps watches on data nodes
* Get settings endpoint modified
Now returns index.routing.allocation.* settings explicitly filters out
the `index.routing.allocation.include._tier_preference` setting
* Tests for modified endpoints
* Update docs
Deprecate to, from, include_lower, include_upper range query params.
These params have been removed from our documentation in v. 0.90.4 (d6ecdecc19),
but did not got through deprecation cycle.
These params to be removed in v9.0.
Related to #81276Closes#48538
<!-- Thank you for your interest in and contributing to Elasticsearch!
There are a few simple things to check before submitting your pull
request that can help with the review process. You should delete these
items from your submission, but they are here to help bring them to your
attention. -->
- Have you signed the [contributor license agreement](https://www.elastic.co/contributor-agreement)?
- Have you followed the [contributor guidelines](https://github.com/elastic/elasticsearch/blob/main/CONTRIBUTING.md)?
- If submitting code, have you built your formula locally prior to submission with `gradle check`?
- If submitting code, is your pull request against main? Unless there is a good reason otherwise, we prefer pull requests against main and will backport as needed.
- If submitting code, have you checked that your submission is for an [OS and architecture that we support](https://www.elastic.co/support/matrix#show_os)?
- If you are submitting this code for a class then read our [policy](https://github.com/elastic/elasticsearch/blob/main/CONTRIBUTING.md#contributing-as-part-of-a-class) for that.
**Problem:**
For historical reasons, source files for the Elasticsearch Guide's security, watcher, and Logstash API docs are housed in the `x-pack/docs` directory. This can confuse new contributors who expect Elasticsearch Guide docs to be located in `docs/reference`.
**Solution:**
- Move the security, watcher, and Logstash API doc source files to the `docs/reference` directory
- Update doc snippet tests to use security
Rel: https://github.com/elastic/platform-docs-team/issues/208
