cloud hosted deployment-templates get-deployment-template-v2 cli command
Elastic Cloud Serverless projects are autoscaled environments, fully managed by Elastic and available on Elastic Cloud. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Serverless interfaces and procedures might differ from classic Elastic Stack deployments. The Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats. Availability This functionality is in technical preview and is ready for evaluation. Use with caution in production; it is not recommended for mission-critical workloads. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Specific Support terms apply. Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments. This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Serverless
Preview
Preview
Stack
Preview
Preview
elastic cloud hosted deployment-templates get-deployment-template-v2 \
--template-id <template-id> \
--region <region> \
[options]
Get deployment template
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--template-idstringrequired- The identifier for the deployment template.
--regionstringrequired- Region of the deployment template
--show-instance-configurations- If true, will return details for each instance configuration referenced by the template.
--show-max-zones- If true, will populate the max_zones field in the instance configurations. Only relevant if show_instance_configurations=true.
--stack-versionstring- If present, it will cause the returned deployment template to be adapted to return only the elements allowed in that version.
--input-filestring- path to a JSON file to use as command input
--dry-run- validate all inputs and exit without performing any action (preview changes without applying them)
--no-validate- skip input validation and send the request as-is
--output-fieldsstring- comma-separated list of fields to include in output (dot-notation supported)
--output-templatestring- Mustache-like template for custom text output (e.g. "{{id}}: {{name}}")
--json-
output as JSON