oci-cli 3.66.1__py3-none-any.whl → 3.67.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-discovery/create-exadb-stack.txt

@@ -0,0 +1,173 @@
+"create-exadb-stack"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new Exadata Fleet Update Discovery.
+
+
+Usage
+=====
+
+   oci fleet-software-update fsu-discovery create-exadb-stack [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+Compartment Identifier.
+
+--details-components [complex type]
+
+Discovery filter details of components in an Exadata software stack.
+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.
+
+--details-service-type [text]
+
+Exadata service type for the target resource members.
+
+Accepted values are:
+
+   EXACC, EXACS
+
+
+Optional Parameters
+===================
+
+--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.
+
+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.
+
+--display-name [text]
+
+Exadata Fleet Update Collection display name.
+
+--freeform-tags [complex type]
+
+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.
+
+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.
+
+--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: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--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:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
+
+--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.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+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 fleet-software-update fsu-discovery create-exadb-stack --generate-param-json-input details-components > details-components.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.
+
+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/fleet-software-update/fsu-discovery/create-exadb-stack.html#cmdoption-compartment-id
+       export details_service_type=<substitute-value-of-details_service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-discovery/create-exadb-stack.html#cmdoption-details-service-type
+
+       oci fleet-software-update fsu-discovery create-exadb-stack --compartment-id $compartment_id --details-components file://details-components.json --details-service-type $details_service_type

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-discovery/create-guest-os.txt

@@ -0,0 +1,185 @@
+"create-guest-os"
+*****************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new Exadata Fleet Update Discovery.
+
+
+Usage
+=====
+
+   oci fleet-software-update fsu-discovery create-guest-os [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+Compartment Identifier.
+
+--details-criteria [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.
+
+--details-service-type [text]
+
+Exadata service type for the target resource members.
+
+Accepted values are:
+
+   EXACC, EXACS
+
+--details-source-major-version [text]
+
+Major version of Exadata Image (Guest OS) release for Exadata VM
+Cluster targets to be included in the results for an Exadata Fleet
+Update Discovery. Major Versions of Exadata Software are demarcated by
+the underlying Oracle Linux OS version. For more details, refer to
+Oracle document 2075007.1
+
+Accepted values are:
+
+   EXA_OL_5, EXA_OL_6, EXA_OL_7, EXA_OL_8
+
+
+Optional Parameters
+===================
+
+--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.
+
+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.
+
+--display-name [text]
+
+Exadata Fleet Update Collection display name.
+
+--freeform-tags [complex type]
+
+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.
+
+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.
+
+--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: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--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:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, NEEDS_ATTENTION, SUCCEEDED, WAITING
+
+--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.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+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 fleet-software-update fsu-discovery create-guest-os --generate-param-json-input details-criteria > details-criteria.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.
+
+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/fleet-software-update/fsu-discovery/create-guest-os.html#cmdoption-compartment-id
+       export details_service_type=<substitute-value-of-details_service_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-discovery/create-guest-os.html#cmdoption-details-service-type
+       export details_source_major_version=<substitute-value-of-details_source_major_version> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/fleet-software-update/fsu-discovery/create-guest-os.html#cmdoption-details-source-major-version
+
+       oci fleet-software-update fsu-discovery create-guest-os --compartment-id $compartment_id --details-criteria file://details-criteria.json --details-service-type $details_service_type --details-source-major-version $details_source_major_version

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update/fsu-discovery.txt

@@ -19,8 +19,12 @@ Available Commands
 
 * create-db
 
+* create-exadb-stack
+
 * create-gi
 
+* create-guest-os
+
 * delete
 
 * get

oci_cli/help_text_producer/data_files/text/cmdref/fleet-software-update.txt

@@ -70,8 +70,12 @@ Available Commands
 
   * create-db
 
+  * create-exadb-stack
+
   * create-gi
 
+  * create-guest-os
+
   * delete
 
   * delete-fsu-collection-target
@@ -112,6 +116,8 @@ Available Commands
 
   * update-fifty-batch
 
+  * update-fsu-cycle-exadb-stack-fsu-goal-version-details
+
   * update-fsu-cycle-update-upgrade-fsu-cycle
 
   * update-image-id-target
@@ -142,8 +148,12 @@ Available Commands
 
   * create-db
 
+  * create-exadb-stack
+
   * create-gi
 
+  * create-guest-os
+
   * delete
 
   * get

oci_cli/help_text_producer/data_files/text/cmdref/fn/function/create.txt

@@ -88,6 +88,21 @@ 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.
 
+--detached-mode-timeout-in-seconds [integer]
+
+Timeout for detached function invocations. Value in seconds.
+
+--failure-destination [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.
+
 --freeform-tags [complex type]
 
 Free-form tags for this resource. Each tag is a simple key-value pair
@@ -171,6 +186,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.
 
+--success-destination [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.
+
 --timeout-in-seconds [integer]
 
 Timeout for executions of the function. Value in seconds.

oci_cli/help_text_producer/data_files/text/cmdref/fn/function/update.txt

@@ -78,6 +78,21 @@ 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.
 
+--detached-mode-timeout-in-seconds [integer]
+
+Timeout for detached function invocations. Value in seconds.
+
+--failure-destination [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.
+
 --force
 
 Perform update without prompting for confirmation.
@@ -161,6 +176,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.
 
+--success-destination [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.
+
 --timeout-in-seconds [integer]
 
 Timeout for executions of the function. Value in seconds.

oci_cli/help_text_producer/data_files/text/cmdref/fusion-apps/fusion-environment/create.txt

@@ -126,6 +126,12 @@ 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
 
+--ipv6-dual-stack-enabled [boolean]
+
+Enable IPv4/IPv6 dual stack support for the environment.  Setting to
+true will assign an IPv6 address to the environment in addition to an
+IPv4 address. Default value will be false if not set
+
 --kms-key-id [text]
 
 byok kms keyId

oci_cli/help_text_producer/data_files/text/cmdref/fusion-apps/fusion-environment/update.txt

@@ -112,6 +112,12 @@ previous GET or POST response for that resource. The resource will be
 updated or deleted only if the etag you provide matches the resource’s
 current etag value.
 
+--ipv6-dual-stack-enabled [boolean]
+
+Enable IPv4/IPv6 dual stack support for the environment.  Setting to
+true will assign an IPv6 address to the environment in addition to an
+IPv4 address.
+
 --kms-key-id [text]
 
 byok kms keyId

oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/endpoint/create.txt

@@ -127,6 +127,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
 
+--generative-ai-private-endpoint-id [text]
+
+The OCID of the Generative AI private endpoint to which this endpoint
+is attached to.
+
 --max-wait-seconds [integer]
 
 The maximum time to wait for the work request to reach the state

oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/endpoint/update.txt

@@ -119,6 +119,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
 
+--generative-ai-private-endpoint-id [text]
+
+The OCID of the Generative AI private endpoint to which this endpoint
+will be attached.
+
 --if-match [text]
 
 For optimistic concurrency control. In the PUT or DELETE call for a

oci_cli/help_text_producer/data_files/text/cmdref/generative-ai/generative-ai-private-endpoint/change-compartment.txt

@@ -0,0 +1,136 @@
+"change-compartment"
+********************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Moves a Generative AI private endpoint into a different compartment.
+When provided, If-Match is checked against ETag values of the
+resource.
+
+
+Usage
+=====
+
+   oci generative-ai generative-ai-private-endpoint change-compartment [OPTIONS]
+
+
+Required Parameters
+===================
+
+--compartment-id, -c [text]
+
+The OCID of the target compartment where the private endpoint is
+moved.
+
+--generative-ai-private-endpoint-id [text]
+
+The unique id for a Generative AI private endpoint.
+
+
+Optional Parameters
+===================
+
+--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: https://docs.cloud.oracle.com/iaas/Conte
+nt/API/SDKDocs/cliusing.htm#AdvancedJSONOptions
+
+--if-match [text]
+
+For optimistic concurrency control. In the PUT or DELETE call for a
+resource, set the *if-match* parameter to the value of the etag from a
+previous GET or POST response for that resource. The resource will be
+updated or deleted only if the etag you provide matches the resource’s
+current etag value.
+
+--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:
+
+   ACCEPTED, CANCELED, CANCELING, FAILED, IN_PROGRESS, SUCCEEDED, WAITING
+
+--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.
+
+
+Global Parameters
+=================
+
+Use "oci --help" for help on global parameters.
+
+"--auth-purpose", "--auth", "--cert-bundle", "--cli-auto-prompt", "--
+cli-rc-file", "--config-file", "--connection-timeout", "--debug", "--
+defaults-file", "--endpoint", "--generate-full-command-json-input", "
+--generate-param-json-input", "--help", "--latest-version", "--max-
+retries", "--no-retry", "--opc-client-request-id", "--opc-request-id",
+"--output", "--profile", "--proxy", "--query", "--raw-output", "--
+read-timeout", "--realm-specific-endpoint", "--region", "--release-
+info", "--request-id", "--version", "-?", "-d", "-h", "-i", "-v"
+
+
+Example using required parameter
+================================
+
+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.
+
+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/generative-ai/generative-ai-private-endpoint/create.html#cmdoption-compartment-id
+       export dns_prefix=<substitute-value-of-dns_prefix> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/generative-ai-private-endpoint/create.html#cmdoption-dns-prefix
+       export subnet_id=<substitute-value-of-subnet_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/generative-ai/generative-ai-private-endpoint/create.html#cmdoption-subnet-id
+
+       generative_ai_private_endpoint_id=$(oci generative-ai generative-ai-private-endpoint create --compartment-id $compartment_id --dns-prefix $dns_prefix --subnet-id $subnet_id --query data.id --raw-output)
+
+       oci generative-ai generative-ai-private-endpoint change-compartment --compartment-id $compartment_id --generative-ai-private-endpoint-id $generative_ai_private_endpoint_id