Skip to content

Extract cron docs from watchers docs#49156

Closed
andrershov wants to merge 1 commit intoelastic:masterfrom
andrershov:cron_docs
Closed

Extract cron docs from watchers docs#49156
andrershov wants to merge 1 commit intoelastic:masterfrom
andrershov:cron_docs

Conversation

@andrershov
Copy link
Copy Markdown
Contributor

@andrershov andrershov commented Nov 15, 2019

Today we have cron expression docs live inside watcher docs. Before "Snapshot lifecycle Management" feature watcher was the only user of Cron.
But now SLM uses Cron as well and it references the subsection inside the Watcher trigger docs.
This PR moves Cron expression docs into elasticsearch-croneval tool docs. Both watcher and SLM now reference this subsection. All further uses of Cron expression might reference this subsection as well.
I'm not sure if elasticsearch-croneval command docs is the best place for cron expressions docs, need reviewers' opinions on that.
This PR also clarifies that all cron schedules are in UTC.
Please let me know you opinion on backporting these changes.

Preview:
http://elasticsearch_49156.docs-preview.app.elstc.co/guide/en/elasticsearch/reference/master/elasticsearch-croneval.html#cron-expressions

@andrershov andrershov added >docs General docs changes :Data Management/ILM+SLM DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead. :Distributed/Watcher v8.0.0 labels Nov 15, 2019
@andrershov andrershov requested review from dakrone and lcawl November 15, 2019 12:31
@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-docs (>docs)

@elasticmachine
Copy link
Copy Markdown
Collaborator

Pinging @elastic/es-core-features (:Core/Features/Watcher)

@lcawl
Copy link
Copy Markdown
Contributor

lcawl commented Nov 15, 2019

In my opinion, that cron reference material could stand alone, even if it's just a sub-page under this command reference.
@jrodewig @debadair : Do you have suggestions / opinions? Should this content go under the eventual "Reference" section?

schedule won't trigger that month.

|======

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It might be nice to add a section or introduction to indicate that the following tables are all examples of cron expressions, unlike the previous tables which were just definitions/explanations.

Copy link
Copy Markdown
Member

@dakrone dakrone left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, I left two comments though, for the clarification one either way is fine, I think the elasticsearch-croneval example should be added back though (unless we were removing a duplicate)

[options="header"]
|======
| Cron Expression | Description
| `0 5 9 * * ?` | Trigger at 9:05 AM every day.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Think it's worth it to change this to:

Suggested change
| `0 5 9 * * ?` | Trigger at 9:05 AM every day.
| `0 5 9 * * ?` | Trigger at 9:05 AM UTC every day.

just to clarify these examples?


[source,bash]
--------------------------------------------------
bin/elasticsearch-croneval "0 0/1 * * * ?"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like this section was removed but didn't make it into the new docs? Was this a duplicate? I think we should probably still include a blurb for how to run this.

@jrodewig
Copy link
Copy Markdown
Contributor

Sorry for the delay in responding @lcawl @debadair .

I'm okay with this living under elasticsearch-croneval for now.

Eventually, it would make sense to move this to a stand-alone page, maybe under "Reference" or it's own page. However, I think we can tackle that as a separate issue later.

@jrodewig
Copy link
Copy Markdown
Contributor

Superseded by #56313

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

:Data Management/ILM+SLM DO NOT USE. Use ":StorageEngine/ILM" or ":Distributed Coordination/SLM" instead. :Distributed/Watcher >docs General docs changes Team:Data Management (obsolete) DO NOT USE. This team no longer exists. Team:Docs Meta label for docs team v8.0.0-alpha1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants