oci-cli 3.64.0__py3-none-any.whl → 3.65.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/generative-ai-inference/chat-result/chat-generic-chat-request.txt

@@ -61,6 +61,10 @@ encourage the model to repeat tokens. Set to 0 to disable.
 Whether to include the user prompt in the response. Applies only to
 non-stream results.
 
+--chat-request-is-parallel-tool-calls [boolean]
+
+Whether to enable parallel function calling during tool use.
+
 --chat-request-is-stream [boolean]
 
 Whether to stream back partial progress. If set to true, as tokens
@@ -94,12 +98,17 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
+--chat-request-max-completion-tokens [integer]
+
+An upper bound for the number of tokens that can be generated for a
+completion, including visible output tokens and reasoning tokens.
+
 --chat-request-max-tokens [integer]
 
 The maximum number of tokens that can be generated per output
-sequence. The token count of your prompt plus *maxTokens* must not
-exceed the model’s context length. Not setting a value for maxTokens
-results in the possible use of model’s full context length.
+sequence. The token count of your prompt plus maxTokens must not
+exceed the model’s context length. For on-demand inferencing, the
+response length is capped at 4,000 tokens for each run.
 
 --chat-request-messages [complex type]
 
@@ -119,10 +128,38 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
+--chat-request-metadata [complex type]
+
+Set of 16 key-value pairs that can be attached to an object. This can
+be useful for storing additional information about the object in a
+structured format, and querying for objects via API or the dashboard.
+
+Keys are strings with a maximum length of 64 characters. Values are
+strings with a maximum length of 512 characters. This is a complex
+type whose value must be valid JSON. The value can be provided as a
+string on the command line or passed in as a file using the
+file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
 --chat-request-num-generations [integer]
 
 The number of of generated texts that will be returned.
 
+--chat-request-prediction [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
 --chat-request-presence-penalty [text]
 
 To reduce repetitiveness of generated tokens, this number penalizes
@@ -135,6 +172,28 @@ present tokens, except that this penalty is applied equally to all
 tokens that have already appeared, regardless of how many times
 they’ve appeared. Set to 0 to disable.
 
+--chat-request-reasoning-effort [text]
+
+Constrains effort on reasoning for reasoning models. Currently
+supported values are minimal, low, medium, and high. Reducing
+reasoning effort can result in faster responses and fewer tokens used
+on reasoning in a response.
+
+Accepted values are:
+
+   HIGH, LOW, MEDIUM, MINIMAL
+
+--chat-request-response-format [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
 --chat-request-seed [integer]
 
 If specified, the backend will make a best effort to sample tokens
@@ -155,6 +214,17 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
+--chat-request-stream-options [complex type]
+
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
+
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
+
 --chat-request-temperature [text]
 
 A number that sets the randomness of the generated output. A lower
@@ -220,6 +290,16 @@ the model eliminates the bottom 25 percent for the next token. Set to
 1 to consider all tokens and set to 0 to disable. If both k and p are
 enabled, p acts after k.
 
+--chat-request-verbosity [text]
+
+Constrains the verbosity of the model’s response. Lower values will
+result in more concise responses, while higher values will result in
+more verbose responses.
+
+Accepted values are:
+
+   HIGH, LOW, MEDIUM
+
 --from-json [text]
 
 Provide input to this command as a JSON document from a file using the

oci_cli/help_text_producer/data_files/text/cmdref/goldengate/deployment/create.txt

@@ -74,6 +74,12 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
+--byol-cpu-core-count-limit [integer]
+
+The maximum number of CPUs allowed with a ‘Bring Your Own License’
+(BYOL) license type. Any CPU usage above this limit is considered as
+License Included and billed.
+
 --certificate-file [filename]
 
 The SSL certificate for this deployment in PEM format.
@@ -198,6 +204,12 @@ The OCID of the Identity Domain when IAM credential store is used.
 Indicates if auto scaling is enabled for the Deployment’s CPU core
 count.
 
+--is-byol-cpu-core-count-limit-enabled [boolean]
+
+Flag to allow to configure the ‘Bring Your Own License’ (BYOL) license
+type CPU limit. If enabled, the exact number of CPUs must be provided
+via byolCpuCoreCountLimit.
+
 --is-public [boolean]
 
 True if this object is publicly available.

oci_cli/help_text_producer/data_files/text/cmdref/goldengate/deployment/list.txt

@@ -56,6 +56,15 @@ assigned.
 
 The OCID of the connection which for the deployment must be assigned.
 
+--deployment-type [text]
+
+A filter that returns only the resources matching the specified
+‘deploymentType’.
+
+Accepted values are:
+
+   BIGDATA, DATABASE_DB2I, DATABASE_DB2ZOS, DATABASE_MICROSOFT_SQLSERVER, DATABASE_MYSQL, DATABASE_ORACLE, DATABASE_POSTGRESQL, DATA_TRANSFORMS, GGSA, OGG
+
 --display-name [text]
 
 A filter to return only the resources that match the entire

oci_cli/help_text_producer/data_files/text/cmdref/goldengate/deployment/update.txt

@@ -61,6 +61,12 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
+--byol-cpu-core-count-limit [integer]
+
+The maximum number of CPUs allowed with a ‘Bring Your Own License’
+(BYOL) license type. Any CPU usage above this limit is considered as
+License Included and billed.
+
 --certificate-file [filename]
 
 The SSL certificate for this deployment in PEM format.
@@ -177,6 +183,12 @@ current etag value.
 Indicates if auto scaling is enabled for the Deployment’s CPU core
 count.
 
+--is-byol-cpu-core-count-limit-enabled [boolean]
+
+Flag to allow to configure the ‘Bring Your Own License’ (BYOL) license
+type CPU limit. If enabled, the exact number of CPUs must be provided
+via byolCpuCoreCountLimit.
+
 --is-lock-override [boolean]
 
 Whether to override locks (if any exist).

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-error/{list.txt → list-errors.txt}

@@ -1,5 +1,5 @@
-"list"
-******
+"list-errors"
+*************
 
 * Description
 
@@ -24,7 +24,7 @@ given ID.
 Usage
 =====
 
-   oci governance-rules-control-plane work-request work-request-error list [OPTIONS]
+   oci governance-rules-control-plane work-request work-request-error list-errors [OPTIONS]
 
 
 Required Parameters
@@ -124,6 +124,6 @@ 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 work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/governance-rules-control-plane/work-request/work-request-error/list.html#cmdoption-work-request-id
+       export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/governance-rules-control-plane/work-request/work-request-error/list-errors.html#cmdoption-work-request-id
 
-       oci governance-rules-control-plane work-request work-request-error list --work-request-id $work_request_id
+       oci governance-rules-control-plane work-request work-request-error list-errors --work-request-id $work_request_id

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-error.txt

@@ -11,4 +11,4 @@ An error encountered while executing a work request.
 Available Commands
 ==================
 
-* list
+* list-errors

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-log-entry/{list-work-request-logs.txt → list-logs.txt}

@@ -1,5 +1,5 @@
-"list-work-request-logs"
-************************
+"list-logs"
+***********
 
 * Description
 
@@ -24,7 +24,7 @@ ID.
 Usage
 =====
 
-   oci governance-rules-control-plane work-request work-request-log-entry list-work-request-logs [OPTIONS]
+   oci governance-rules-control-plane work-request work-request-log-entry list-logs [OPTIONS]
 
 
 Required Parameters
@@ -124,6 +124,6 @@ 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 work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/governance-rules-control-plane/work-request/work-request-log-entry/list-work-request-logs.html#cmdoption-work-request-id
+       export work_request_id=<substitute-value-of-work_request_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/governance-rules-control-plane/work-request/work-request-log-entry/list-logs.html#cmdoption-work-request-id
 
-       oci governance-rules-control-plane work-request work-request-log-entry list-work-request-logs --work-request-id $work_request_id
+       oci governance-rules-control-plane work-request work-request-log-entry list-logs --work-request-id $work_request_id

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request/work-request-log-entry.txt

@@ -11,4 +11,4 @@ A log message from the execution of a work request.
 Available Commands
 ==================
 
-* list-work-request-logs
+* list-logs

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane/work-request.txt

@@ -21,8 +21,8 @@ Available Commands
 
 * work-request-error
 
-  * list
+  * list-errors
 
 * work-request-log-entry
 
-  * list-work-request-logs
+  * list-logs

oci_cli/help_text_producer/data_files/text/cmdref/governance-rules-control-plane.txt

@@ -77,8 +77,8 @@ Available Commands
 
   * work-request-error
 
-    * list
+    * list-errors
 
   * work-request-log-entry
 
-    * list-work-request-logs
+    * list-logs

oci_cli/help_text_producer/data_files/text/cmdref/{service-mesh/mesh/delete.txt → kafka/cluster/change-compartment.txt}

@@ -1,5 +1,5 @@
-"delete"
-********
+"change-compartment"
+********************
 
 * Description
 
@@ -17,29 +17,31 @@
 Description
 ===========
 
-Deletes a Mesh resource by identifier.
+Moves a KafkaCluster into a different compartment within the same
+tenancy. For information about moving resources between compartments,
+see Moving Resources to a Different Compartment.
 
 
 Usage
 =====
 
-   oci service-mesh mesh delete [OPTIONS]
+   oci kafka cluster change-compartment [OPTIONS]
 
 
 Required Parameters
 ===================
 
---mesh-id [text]
+--compartment-id, -c [text]
 
-Unique Mesh identifier.
+The OCID of the compartment to move the KafkaCluster to.
 
+--kafka-cluster-id [text]
 
-Optional Parameters
-===================
+The OCID of the KafkaCluster.
 
---force
 
-Perform deletion without prompting for confirmation.
+Optional Parameters
+===================
 
 --from-json [text]
 
@@ -116,11 +118,6 @@ info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
 Example using required parameter
 ================================
 
-Copy and paste the following example into a JSON file, replacing the
-example parameters with your own.
-
-       oci service-mesh mesh create --generate-param-json-input certificate-authorities > certificate-authorities.json
-
 Copy the following CLI commands into a file named example.sh. Run the
 command by typing “bash example.sh” and replacing the example
 parameters with your own.
@@ -129,9 +126,7 @@ 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/service-mesh/mesh/create.html#cmdoption-compartment-id
-       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/service-mesh/mesh/create.html#cmdoption-display-name
-
-       mesh_id=$(oci service-mesh mesh create --certificate-authorities file://certificate-authorities.json --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/change-compartment.html#cmdoption-compartment-id
+       export kafka_cluster_id=<substitute-value-of-kafka_cluster_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/change-compartment.html#cmdoption-kafka-cluster-id
 
-       oci service-mesh mesh delete --mesh-id $mesh_id
+       oci kafka cluster change-compartment --compartment-id $compartment_id --kafka-cluster-id $kafka_cluster_id

oci_cli/help_text_producer/data_files/text/cmdref/{service-mesh/virtual-service → kafka/cluster}/create.txt

@@ -17,41 +17,84 @@
 Description
 ===========
 
-Creates a new VirtualService.
+Creates a KafkaCluster.
 
 
 Usage
 =====
 
-   oci service-mesh virtual-service create [OPTIONS]
+   oci kafka cluster create [OPTIONS]
 
 
 Required Parameters
 ===================
 
---compartment-id, -c [text]
+--access-subnets [complex type]
 
-The OCID of the compartment.
+Subnets where broker/coordinator VNICs will be created. This is a
+complex type whose value must be valid JSON. The value can be provided
+as a string on the command line or passed in as a file using the
+file://path/to/file syntax.
 
---mesh-id [text]
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
 
-The OCID of the service mesh in which this virtual service is created.
+--broker-shape [complex type]
 
---name [text]
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
 
-A user-friendly name. The name has to be unique within the same
-service mesh and cannot be changed after creation. Avoid entering
-confidential information.
+The "--generate-param-json-input" option can be used to generate an
+example of the JSON which must be provided. We recommend storing this
+example in a file, modifying it as needed and then passing it back in
+via the file:// syntax.
 
-Example:
+--cluster-config-id [text]
 
-   My unique resource name
+The OCID of Kafka Cluster configuration object
+
+--cluster-config-version [integer]
+
+The version of configuration object
+
+--cluster-type [text]
+
+Type of the cluster to spin up. DEVELOPMENT - setting that allows to
+sacrifice HA and spin up cluster on single node PRODUCTION - Minimum
+allowed broker count is 3
+
+--compartment-id, -c [text]
+
+The OCID of the compartment to create the KafkaCluster in.
+
+--coordination-type [text]
+
+Kafka coordination type. Set of available types depends on Kafka
+version
+
+--kafka-version [text]
+
+Version of Kafka to use to spin up the cluster
 
 
 Optional Parameters
 ===================
 
---default-routing-policy [complex type]
+--client-certificate-bundle [text]
+
+CA certificate bundle for mTLS broker authentication.
+
+--defined-tags [complex type]
+
+Defined tags for this resource. Each key is predefined and scoped to a
+namespace. For more information, see Resource Tags.
+
+Example:
+
+   {"Operations": {"CostCenter": "42"}}
 
 This is a complex type whose value must be valid JSON. The value can
 be provided as a string on the command line or passed in as a file
@@ -62,35 +105,24 @@ example of the JSON which must be provided. We recommend storing this
 example in a file, modifying it as needed and then passing it back in
 via the file:// syntax.
 
---defined-tags [complex type]
-
-Defined tags for this resource. Each key is predefined and scoped to a
-namespace. Example: *{“foo-namespace”: {“bar-key”: “value”}}* This is
-a complex type whose value must be valid JSON. The value can be
-provided as a string on the command line or passed in as a file using
-the file://path/to/file syntax.
+--display-name [text]
 
-The "--generate-param-json-input" option can be used to generate an
-example of the JSON which must be provided. We recommend storing this
-example in a file, modifying it as needed and then passing it back in
-via the file:// syntax.
+A user-friendly name. Does not have to be unique, and it’s changeable.
+Avoid entering confidential information.
 
---description [text]
+--freeform-tags [complex type]
 
-Description of the resource. It can be changed after creation. Avoid
-entering confidential information.
+Free-form tags for this resource. Each tag is a simple key-value pair
+with no predefined name, type, or namespace. For more information, see
+Resource Tags.
 
 Example:
 
-   This is my new resource
-
---freeform-tags [complex type]
+   {"Department": "Finance"}
 
-Simple key-value pair that is applied without any predefined name,
-type or scope. Exists for cross-compatibility only. Example: *{“bar-
-key”: “value”}* This is a complex type whose value must be valid JSON.
-The value can be provided as a string on the command line or passed in
-as a file using the file://path/to/file syntax.
+This is a complex type whose value must be valid JSON. The value can
+be provided as a string on the command line or passed in as a file
+using the file://path/to/file syntax.
 
 The "--generate-param-json-input" option can be used to generate an
 example of the JSON which must be provided. We recommend storing this
@@ -119,37 +151,11 @@ For examples on usage of this option, please see our “using CLI with
 advanced JSON options” link: https://docs.cloud.oracle.com/iaas/Conte
 nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
 
---hosts [complex type]
-
-The DNS hostnames of the virtual service that is used by its callers.
-Wildcard hostnames are supported in the prefix form. Examples of valid
-hostnames are “www.example.com”, “*.example.com”, “*.com”. Can be
-omitted if the virtual service will only have TCP virtual deployments.
-This is a complex type whose value must be valid JSON. The value can
-be provided as a string on the command line or passed in as a file
-using the file://path/to/file syntax.
-
-The "--generate-param-json-input" option can be used to generate an
-example of the JSON which must be provided. We recommend storing this
-example in a file, modifying it as needed and then passing it back in
-via the file:// syntax.
-
 --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.
 
---mtls [complex type]
-
-This is a complex type whose value must be valid JSON. The value can
-be provided as a string on the command line or passed in as a file
-using the file://path/to/file syntax.
-
-The "--generate-param-json-input" option can be used to generate an
-example of the JSON which must be provided. We recommend storing this
-example in a file, modifying it as needed and then passing it back in
-via the file:// syntax.
-
 --wait-for-state [text]
 
 This operation asynchronously creates, modifies or deletes a resource
@@ -193,7 +199,10 @@ Example using required parameter
 Copy and paste the following example into a JSON file, replacing the
 example parameters with your own.
 
-       oci service-mesh mesh create --generate-param-json-input certificate-authorities > certificate-authorities.json
+       oci kafka cluster-config create --generate-param-json-input latest-config > latest-config.json
+
+       oci kafka cluster create --generate-param-json-input access-subnets > access-subnets.json
+       oci kafka cluster create --generate-param-json-input broker-shape > broker-shape.json
 
 Copy the following CLI commands into a file named example.sh. Run the
 command by typing “bash example.sh” and replacing the example
@@ -203,9 +212,12 @@ 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/service-mesh/mesh/create.html#cmdoption-compartment-id
-       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/service-mesh/mesh/create.html#cmdoption-display-name
+       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster-config/create.html#cmdoption-compartment-id
+       export cluster_config_version=<substitute-value-of-cluster_config_version> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/create.html#cmdoption-cluster-config-version
+       export cluster_type=<substitute-value-of-cluster_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/create.html#cmdoption-cluster-type
+       export coordination_type=<substitute-value-of-coordination_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/create.html#cmdoption-coordination-type
+       export kafka_version=<substitute-value-of-kafka_version> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/create.html#cmdoption-kafka-version
 
-       mesh_id=$(oci service-mesh mesh create --certificate-authorities file://certificate-authorities.json --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
+       cluster_config_id=$(oci kafka cluster-config create --compartment-id $compartment_id --latest-config file://latest-config.json --query data.id --raw-output)
 
-       oci service-mesh virtual-service create --compartment-id $compartment_id --mesh-id $mesh_id --name $name
+       oci kafka cluster create --access-subnets file://access-subnets.json --broker-shape file://broker-shape.json --cluster-config-id $cluster_config_id --cluster-config-version $cluster_config_version --cluster-type $cluster_type --compartment-id $compartment_id --coordination-type $coordination_type --kafka-version $kafka_version

oci_cli/help_text_producer/data_files/text/cmdref/{anomaly-detection/project → kafka/cluster}/delete.txt

@@ -17,24 +17,21 @@
 Description
 ===========
 
-Deletes a Project resource by identifier. This operation fails with a
-409 error unless all associated resources (models deployments or data
-assets) are in a DELETED state. You must delete all associated
-resources before deleting a project.
+Deletes a KafkaCluster.
 
 
 Usage
 =====
 
-   oci anomaly-detection project delete [OPTIONS]
+   oci kafka cluster delete [OPTIONS]
 
 
 Required Parameters
 ===================
 
---project-id [text]
+--kafka-cluster-id [text]
 
-The OCID of the Project.
+The OCID of the KafkaCluster.
 
 
 Optional Parameters
@@ -92,7 +89,7 @@ of 2 is returned. For any other error, a return code of 1 is returned.
 
 Accepted values are:
 
-   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, SUCCEEDED, WAITING
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
 
 --wait-interval-seconds [integer]
 
@@ -127,8 +124,6 @@ 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/anomaly-detection/project/create.html#cmdoption-compartment-id
+       export kafka_cluster_id=<substitute-value-of-kafka_cluster_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/kafka/cluster/delete.html#cmdoption-kafka-cluster-id
 
-       project_id=$(oci anomaly-detection project create --compartment-id $compartment_id --query data.id --raw-output)
-
-       oci anomaly-detection project delete --project-id $project_id
+       oci kafka cluster delete --kafka-cluster-id $kafka_cluster_id