cloud hosted deployments update-deployment 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 deployments update-deployment \
--deployment-id <deployment-id> \
--prune-orphans \
[options]
Update Deployment
Behaviour flags:
--dry-run — validate all inputs and exit without performing any action
--deployment-idstringrequired- Identifier for the Deployment
--prune-orphansrequired--hide-pruned-orphans- Whether or not to hide orphaned resources that were shut down (relevant if prune on the request is true)
--skip-snapshot- Whether or not to skip snapshots before shutting down orphaned resources (relevant if prune on the request is true)
--validate-only- If true, will just validate the Deployment definition but will not perform the update
--versionstring- If specified then checks for conflicts against the version stored in the persistent store (returned in 'x-cloud-resource-version' of the GET request)
--namestring--resourcesstring--settingsstring--metadatastring--aliasstring--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
--yes- confirm destructive action without prompting
--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