resize-datalake¶

Description¶

Resizes the datalake to the given size.

Synopsis¶

  resize-datalake
--datalake-name <value>
--target-size <value>
[--multi-az | --no-multi-az]
[--custom-instance-types <value>]
[--custom-instance-disks <value>]
[--custom-database-compute-storage <value>]
[--skip-validation | --no-skip-validation]
[--validation-only | --no-validation-only]
[--cli-input-json <value>]
[--generate-cli-skeleton]

Options¶

--datalake-name (string)

The name or CRN of the datalake.

--target-size (string)

The target size for the datalake. The resize target size can be MEDIUM_DUTY or ENTERPRISE. If the runtime version >= 7.2.17 target size is ENTERPRISE. If not, the target size is MEDIUM_DUTY.

Possible values:

• MEDIUM_DUTY_HA

• ENTERPRISE

--multi-az | --no-multi-az (boolean)

Whether to deploy a new datalake in a multi-availability zone way.

--custom-instance-types (array)

Any custom instance type to override defaults.

Shorthand Syntax:

name=string,instanceType=string ... (separate items with spaces)

JSON Syntax:

[
  {
    "name": "string",
    "instanceType": "string"
  }
  ...
]

--custom-instance-disks (array)

Any custom instance disk size to override defaults.

Shorthand Syntax:

name=string,diskSize=integer ... (separate items with spaces)

JSON Syntax:

[
  {
    "name": "string",
    "diskSize": integer
  }
  ...
]

--custom-database-compute-storage (object)

Request object for modified database storage properties.

instanceType -> (string)

The modified instance type.

storageSize -> (integer)

The modified storage size for the database.

Shorthand Syntax:

instanceType=string,storageSize=integer

JSON Syntax:

{
  "instanceType": "string",
  "storageSize": integer
}

--skip-validation | --no-skip-validation (boolean)

Skips the validation steps that run prior to the resize. If this option is not provided, the validations are performed by default. If skip-validation and validation-only are used together an error is thrown.

--validation-only | --no-validation-only (boolean)

Runs only the validation steps and then returns. If this option is not provided, the resize is performed as normal by default. If skip-validation and validation-only are used together an error is thrown.

--cli-input-json (string)

Performs service operation based on the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton. If other arguments are provided on the command line, the CLI values will override the JSON-provided values.

--generate-cli-skeleton (boolean)

Prints a sample input JSON to standard output. Note the specified operation is not run if this argument is specified. The sample input can be used as an argument for --cli-input-json.

Output¶

datalakeName -> (string)

The name of the datalake. This will remain the same for the datalake created by the resize process.

datalakeCrn -> (string)

The CRN of the datalake. This will remain the same for the datalake created by the resize process.

environmentCrn -> (string)

The CRN of the environment the datalake is attached to. This will remain the same for the datalake created by the resize process.

runtime -> (string)

The runtime of the datalake. This will remain the same for the datalake created by the resize process.

status -> (string)

The current status of the datalake.

statusReason -> (string)

The reason for the current status of the datalake.

cloudbreakVersion -> (string)

The Cloudbreak version used to create the data lake.

tags -> (array)

Datalake tags object containing the tag values defined for the datalake.

item -> (object)

Tag for a datalake resource.

key -> (string)

The key of tag.

value -> (string)

The value of the tag.

operationId -> (string)

Unique operation ID assigned to this command execution. Use this identifier with ‘get-operation’ to track status and retrieve detailed results.

Form Factors¶

public