Audit CLI Script

[kevinfodness]

Description

Anecdotally, we've had some trouble running the index command on Pantheon via Terminus when using Elastic Cloud on 8.x. Symptoms include:

1. Timeouts. We're hitting 10s timeouts when attempting to do things like flush the index or put the mapping. Unclear where this is coming from.
2. Failures to flush or put the mapping. Perhaps flush is failing if the index is already empty or doesn't exist? Perhaps a different cause?
3. Intermittent failures to bulk index, which could be related to timeouts or could be a separate issue entirely.

We need to audit the CLI script for indexing, including the options for flushing and putting the mapping, to make it more reliable.

Use Case

As a developer, I want to be able to reindex a site using the CLI including flushing the old index and putting the mapping without encountering errors.

[mboynes]

Additional notes/ideas:

• Improve error handling and reporting. If a post fails, identify which one(s) failed and try to figure out why.
• Automatic retries and self-adjustment. If a request times out, split the batch in two and try again. Repeat n times.
• Add a progress bar. Maybe leverage https://github.com/alleyinteractive/wp-bulk-task?
  • If we don't leverage WP Bulk Task, then ensure that the CLI script is cursoring through content instead of paginating through it.
• When running the index command, automatically --put-mapping if --flush is included. I don't think there's a circumstance where we'd want to flush without adding the mapping, so that begs for trouble. Alternatively, we could include an option to --skip-mapping if there was a reason (I don't think it's necessary; decisions over options)
• Add some additional basic commands to interact with ES, e.g. get a post, run a search, etc.