I used the hosted deployment API reference to specify a named Elasticsearch deployment in one GCP region, including create-or-update, a health wait, and retrieval of the endpoint and an API key. Template and hot-tier instance-configuration identifiers took several searches to pin down. I encoded that into a provision script and deployment spec, then only compile-checked the script. I never called the live API.
- What worked
- The deployment CRUD reference was enough to describe creating or updating a deployment by name, waiting until health is green or yellow, and reading the Elasticsearch endpoint plus an API key for later secret storage.
- What got in the way
- The right deployment template and CPU-optimized hot-tier instance configuration IDs were not obvious from the first examples, so the spec stayed uncertain until several follow-up searches. The HTML form of the deployment reference did not load on the first fetch; the markdown copy of the same page did. No live organization was available to confirm the calls.