Add a nodeReplaceConfigurations to the cluster.


oci bds instance create-node-replace-configuration-node-type-level-details [OPTIONS]

Required Parameters

--bds-instance-id [text]

The OCID of the cluster.

--cluster-admin-password [text]

Base-64 encoded password for the cluster admin user.

--duration-in-minutes [integer]

This value is the minimum period of time to wait before triggering node replacement. The value is in minutes.

--level-type-details-node-type [text]

Type of the node or nodes of the node backup configuration or node replacement configuration which are going to be created.

--metric-type [text]

Type of compute instance health metric to use for node replacement

Optional Parameters

--display-name [text]

A user-friendly name. Only ASCII alphanumeric characters with no spaces allowed. The name does not have to be unique, and it may be changed. Avoid entering confidential information.

--from-json [text]

Provide input to this command as a JSON document from a file using the file://path-to/file syntax.

The --generate-full-command-json-input option can be used to generate a sample json file to be used with this command option. The key names are pre-populated and match the command option names (converted to camelCase format, e.g. compartment-id –> compartmentId), while the values of the keys need to be populated by the user before using the sample file as an input to this command. For any command option that accepts multiple values, the value of the key can be a JSON array.

Options can still be provided on the command line. If an option exists in both the JSON document and the command line then the command line specified value will be used.

For examples on usage of this option, please see our “using CLI with advanced JSON options” link:

--max-wait-seconds [integer]

The maximum time to wait for the work request to reach the state defined by --wait-for-state. Defaults to 1200 seconds.

--wait-for-state [text]

This operation asynchronously creates, modifies or deletes a resource and uses a work request to track the progress of the operation. Specify this option to perform the action and then wait until the work request reaches a certain state. Multiple states can be specified, returning on the first state. For example, --wait-for-state SUCCEEDED --wait-for-state FAILED would return on whichever lifecycle state is reached first. If timeout is reached, a return code of 2 is returned. For any other error, a return code of 1 is returned.

Accepted values are:

--wait-interval-seconds [integer]

Check every --wait-interval-seconds to see whether the work request has reached the state defined by --wait-for-state. Defaults to 30 seconds.

Example using required parameter

Copy the following CLI commands into a file named Run the command by typing “bash” and replacing the example parameters with your own.

Please note this sample will only work in the POSIX-compliant bash-like shell. You need to set up the OCI configuration and appropriate security policies before trying the examples.

    export bds_instance_id=<substitute-value-of-bds_instance_id> #
    export cluster_admin_password=<substitute-value-of-cluster_admin_password> #
    export duration_in_minutes=<substitute-value-of-duration_in_minutes> #
    export level_type_details_node_type=<substitute-value-of-level_type_details_node_type> #
    export metric_type=<substitute-value-of-metric_type> #

    oci bds instance create-node-replace-configuration-node-type-level-details --bds-instance-id $bds_instance_id --cluster-admin-password $cluster_admin_password --duration-in-minutes $duration_in_minutes --level-type-details-node-type $level_type_details_node_type --metric-type $metric_type