cloud hosted deployments get-deployment-es-resource-info cli command

Auth required

		elastic cloud hosted deployments get-deployment-es-resource-info \
  --deployment-id <deployment-id> \
  --ref-id <ref-id> \
  [options]
		
	

Get Deployment Elasticsearch Resource Info

Behaviour flags:

--dry-run — validate all inputs and exit without performing any action

Options

--deployment-id string required: Identifier for the Deployment
--ref-id string required: User-specified RefId for the Resource (or '_main' if there is only one).
--show-security: Whether to include the Elasticsearch 2.x security information in the response - can be large per cluster and also include credentials.
--show-metadata: Whether to include the full cluster metadata in the response - can be large per cluster and also include credentials.
--show-plans: Whether to include the full current and pending plan information in the response - can be large per cluster.
--show-plan-logs: Whether to include with the current and pending plan information the attempt log - can be very large per cluster.
--show-plan-history: Whether to include with the current and pending plan information the plan history- can be very large per cluster.
--show-plan-defaults: If showing plans, whether to show values that are left at their default value (less readable but more informative).
--convert-legacy-plans: If showing plans, whether to leave pre-2.0.0 plans in their legacy format (the default), or whether to update them to 2.0.x+ format (if 'true').
--show-system-alerts number: Number of system alerts (such as forced restarts due to memory limits) to be included in the response - can be large per cluster. Negative numbers or 0 will not return field.
--show-settings: Whether to show cluster settings in the response.
--enrich-with-template: If showing plans, whether to enrich the plan by including the missing elements from the deployment template it is based on.
--clear-transient: If set (defaults to false) then removes the transient section from all child resources, making it safe to reapply via an update
--input-file string: 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)

Global Options

--json: output as JSON