Allows you to update code configuration on a running cluster. By using this API you can update the code, the initialization script path, and the command line arguments for a specific cluster. The configuration that you want to update will override any existing configurations on the cluster.
See also: AWS API Documentation
update-kx-cluster-code-configuration
--environment-id <value>
--cluster-name <value>
[--client-token <value>]
--code <value>
[--initialization-script <value>]
[--command-line-arguments <value>]
[--deployment-configuration <value>]
[--cli-input-json | --cli-input-yaml]
[--generate-cli-skeleton <value>]
[--debug]
[--endpoint-url <value>]
[--no-verify-ssl]
[--no-paginate]
[--output <value>]
[--query <value>]
[--profile <value>]
[--region <value>]
[--version <value>]
[--color <value>]
[--no-sign-request]
[--ca-bundle <value>]
[--cli-read-timeout <value>]
[--cli-connect-timeout <value>]
[--cli-binary-format <value>]
[--no-cli-pager]
[--cli-auto-prompt]
[--no-cli-auto-prompt]
--environment-id
(string)
A unique identifier of the kdb environment.
--cluster-name
(string)
The name of the cluster.
--client-token
(string)
A token that ensures idempotency. This token expires in 10 minutes.
--code
(structure)
The structure of the customer code available within the running cluster.
s3Bucket -> (string)
A unique name for the S3 bucket.s3Key -> (string)
The full S3 path (excluding bucket) to the .zip file. This file contains the code that is loaded onto the cluster when it’s started.s3ObjectVersion -> (string)
The version of an S3 object.
Shorthand Syntax:
s3Bucket=string,s3Key=string,s3ObjectVersion=string
JSON Syntax:
{
"s3Bucket": "string",
"s3Key": "string",
"s3ObjectVersion": "string"
}
--initialization-script
(string)
Specifies a Q program that will be run at launch of a cluster. It is a relative path within .zip file that contains the custom code, which will be loaded on the cluster. It must include the file name itself. For example,
somedir/init.q
.You cannot update this parameter for a
NO_RESTART
deployment.
--command-line-arguments
(list)
Specifies the key-value pairs to make them available inside the cluster.
You cannot update this parameter for a
NO_RESTART
deployment.(structure)
Defines the key-value pairs to make them available inside the cluster.
key -> (string)
The name of the key.value -> (string)
The value of the key.
Shorthand Syntax:
key=string,value=string ...
JSON Syntax:
[
{
"key": "string",
"value": "string"
}
...
]
--deployment-configuration
(structure)
The configuration that allows you to choose how you want to update the code on a cluster.
deploymentStrategy -> (string)
The type of deployment that you want on a cluster.
- ROLLING – This options updates the cluster by stopping the exiting q process and starting a new q process with updated configuration.
- NO_RESTART – This option updates the cluster without stopping the running q process. It is only available for
GP
type cluster. This option is quicker as it reduces the turn around time to update configuration on a cluster. With this deployment mode, you cannot update theinitializationScript
andcommandLineArguments
parameters.- FORCE – This option updates the cluster by immediately stopping all the running processes before starting up new ones with the updated configuration.
Shorthand Syntax:
deploymentStrategy=string
JSON Syntax:
{
"deploymentStrategy": "NO_RESTART"|"ROLLING"|"FORCE"
}
--cli-input-json
| --cli-input-yaml
(string)
Reads arguments from the JSON string provided. The JSON string follows the format provided by --generate-cli-skeleton
. If other arguments are provided on the command line, those values will override the JSON-provided values. It is not possible to pass arbitrary binary values using a JSON-provided value as the string will be taken literally. This may not be specified along with --cli-input-yaml
.
--generate-cli-skeleton
(string)
Prints a JSON skeleton to standard output without sending an API request. If provided with no value or the value input
, prints a sample input JSON that can be used as an argument for --cli-input-json
. Similarly, if provided yaml-input
it will print a sample input YAML that can be used with --cli-input-yaml
. If provided with the value output
, it validates the command inputs and returns a sample output JSON for that command. The generated JSON skeleton is not stable between versions of the AWS CLI and there are no backwards compatibility guarantees in the JSON skeleton generated.
--debug
(boolean)
Turn on debug logging.
--endpoint-url
(string)
Override command’s default URL with the given URL.
--no-verify-ssl
(boolean)
By default, the AWS CLI uses SSL when communicating with AWS services. For each SSL connection, the AWS CLI will verify SSL certificates. This option overrides the default behavior of verifying SSL certificates.
--no-paginate
(boolean)
Disable automatic pagination. If automatic pagination is disabled, the AWS CLI will only make one call, for the first page of results.
--output
(string)
The formatting style for command output.
--query
(string)
A JMESPath query to use in filtering the response data.
--profile
(string)
Use a specific profile from your credential file.
--region
(string)
The region to use. Overrides config/env settings.
--version
(string)
Display the version of this tool.
--color
(string)
Turn on/off color output.
--no-sign-request
(boolean)
Do not sign requests. Credentials will not be loaded if this argument is provided.
--ca-bundle
(string)
The CA certificate bundle to use when verifying SSL certificates. Overrides config/env settings.
--cli-read-timeout
(int)
The maximum socket read time in seconds. If the value is set to 0, the socket read will be blocking and not timeout. The default value is 60 seconds.
--cli-connect-timeout
(int)
The maximum socket connect time in seconds. If the value is set to 0, the socket connect will be blocking and not timeout. The default value is 60 seconds.
--cli-binary-format
(string)
The formatting style to be used for binary blobs. The default format is base64. The base64 format expects binary blobs to be provided as a base64 encoded string. The raw-in-base64-out format preserves compatibility with AWS CLI V1 behavior and binary values must be passed literally. When providing contents from a file that map to a binary blob fileb://
will always be treated as binary and use the file contents directly regardless of the cli-binary-format
setting. When using file://
the file contents will need to properly formatted for the configured cli-binary-format
.
--no-cli-pager
(boolean)
Disable cli pager for output.
--cli-auto-prompt
(boolean)
Automatically prompt for CLI input parameters.
--no-cli-auto-prompt
(boolean)
Disable automatically prompt for CLI input parameters.
None