oci-cli 3.71.1__py3-none-any.whl → 3.71.3__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/identity-domains/mapped-attribute/search.txt

@@ -0,0 +1,199 @@
+"search"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Search Mapped Attributes Using POST
+
+The top level –endpoint parameter must be supplied for this operation.
+
+
+Usage
+=====
+
+   oci identity-domains mapped-attribute search [OPTIONS]
+
+
+Required Parameters
+===================
+
+--schemas [complex type]
+
+The schemas attribute is an array of Strings which allows
+introspection of the supported schema version for a SCIM
+representation as well any schema extensions supported by that
+representation. Each String value must be a unique URI. Query requests
+MUST be identified using the following URI:
+“urn:ietf:params:scim:api:messages:2.0:SearchRequest” REQUIRED. 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.
+
+
+Optional Parameters
+===================
+
+--attribute-sets [text]
+
+A multi-valued list of strings indicating the return type of attribute
+definition. The specified set of attributes can be fetched by the
+return type of the attribute. One or more values can be given together
+to fetch more than one group of attributes. If “attributes” query
+parameter is also available, union of the two is fetched. Valid values
+: all, always, never, request, default. Values are case-insensitive.
+OPTIONAL.
+
+Accepted values are:
+
+   all, always, default, never, request
+
+--attributes [complex type]
+
+A multi-valued list of strings indicating the names of resource
+attributes to return in the response overriding the set of attributes
+that would be returned by default. Attribute names MUST be in standard
+attribute notation (Section 3.10) form. See (additional retrieval
+query parameters). OPTIONAL. 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.
+
+--authorization [text]
+
+The Authorization field value consists of credentials containing the
+authentication information of the user agent for the realm of the
+resource being requested.
+
+--count [integer]
+
+An integer that indicates the desired maximum number of query results
+per page. 1000 is the largest value that you can use. See the
+Pagination section of the System for Cross-Domain Identity Management
+Protocol specification for more information. (Section 3.4.2.4).
+OPTIONAL.
+
+--filter [text]
+
+The filter string that is used to request a subset of resources. The
+filter string MUST be a valid filter expression. See Section 3.4.2.2.
+OPTIONAL.
+
+--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
+
+--limit [integer]
+
+The maximum number of items to return in a paginated ‘List’ call.
+
+--page [text]
+
+The value of the *opc-next-page* response header from the previous
+‘List’ call.
+
+--resource-type-schema-version [text]
+
+An endpoint-specific schema version number to use in the Request.
+Allowed version values are Earliest Version or Latest Version as
+specified in each REST API endpoint description, or any sequential
+number inbetween. All schema attributes/body parameters are a part of
+version 1. After version 1, any attributes added or deprecated will be
+tagged with the version that they were added to or deprecated in. If
+no version is provided, the latest schema version is returned.
+
+--sort-by [text]
+
+A string that indicates the attribute whose value SHALL be used to
+order the returned responses. The sortBy attribute MUST be in standard
+attribute notation (Section 3.10) form. See Sorting section. OPTIONAL.
+
+--sort-order [text]
+
+A string that indicates the order in which the sortBy parameter is
+applied. Allowed values are “ascending” and “descending”. See (Sorting
+Section). OPTIONAL.
+
+Accepted values are:
+
+   ASCENDING, DESCENDING
+
+--start-index [integer]
+
+An integer that indicates the 1-based index of the first query result.
+See Pagination Section. OPTIONAL.
+
+
+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", "--enable-dual-stack", "--enable-propagation", "--
+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 identity-domains mapped-attribute search --generate-param-json-input schemas > schemas.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.
+
+       oci identity-domains mapped-attribute search --schemas file://schemas.json

oci_cli/help_text_producer/data_files/text/cmdref/identity-domains/mapped-attribute.txt

@@ -0,0 +1,22 @@
+mapped-attribute
+****************
+
+
+Description
+===========
+
+Schema for MappedAttribute resource.
+
+
+Available Commands
+==================
+
+* get
+
+* list
+
+* patch
+
+* put
+
+* search

oci_cli/help_text_producer/data_files/text/cmdref/identity-domains.txt

@@ -376,6 +376,18 @@ Available Commands
 
   * search
 
+* mapped-attribute
+
+  * get
+
+  * list
+
+  * patch
+
+  * put
+
+  * search
+
 * me
 
   * create

oci_cli/help_text_producer/data_files/text/cmdref/integration/integration-instance/change-private-endpoint-outbound-connection-private-endpoint-outbound-connection.txt

@@ -77,6 +77,11 @@ current etag value.
 The maximum time to wait for the work request to reach the state
 defined by "--wait-for-state". Defaults to 1200 seconds.
 
+--private-endpoint-outbound-connection-is-all-outbound-traffic-private [boolean]
+
+Indicates if all traffic should go through configured outbound
+connection
+
 --private-endpoint-outbound-connection-nsg-ids [complex type]
 
 One or more Network security group Ids. This is an optional argument.

oci_cli/help_text_producer/data_files/text/cmdref/integration/integration-instance/convert-instance.txt

@@ -0,0 +1,144 @@
+"convert-instance"
+******************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Integration instance identified by ID will be migrated to a new
+Disaster Recovery enabled integration instance. If a given Integration
+instance has certain features enabled which are not supported for
+conversion/migration it will not be accepted for conversion.
+
+
+Usage
+=====
+
+   oci integration integration-instance convert-instance [OPTIONS]
+
+
+Required Parameters
+===================
+
+--conversion-type [text]
+
+Convert given instance to specified DR instance
+
+Accepted values are:
+
+   DISASTER_RECOVERY
+
+--integration-instance-id [text]
+
+Unique Integration Instance identifier.
+
+
+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
+
+--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", "--enable-dual-stack", "--enable-propagation", "--
+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/integration/integration-instance/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/integration/integration-instance/create.html#cmdoption-display-name
+       export is_byol=<substitute-value-of-is_byol> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-is-byol
+       export message_packs=<substitute-value-of-message_packs> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-message-packs
+       export type=<substitute-value-of-type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-type
+       export conversion_type=<substitute-value-of-conversion_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/convert-instance.html#cmdoption-conversion-type
+
+       integration_instance_id=$(oci integration integration-instance create --compartment-id $compartment_id --display-name $display_name --is-byol $is_byol --message-packs $message_packs --type $type --query data.id --raw-output)
+
+       oci integration integration-instance convert-instance --conversion-type $conversion_type --integration-instance-id $integration_instance_id

oci_cli/help_text_producer/data_files/text/cmdref/integration/integration-instance/disable-process-automation.txt

@@ -0,0 +1,132 @@
+"disable-process-automation"
+****************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Disable Process Automation for given Integration Instance
+
+
+Usage
+=====
+
+   oci integration integration-instance disable-process-automation [OPTIONS]
+
+
+Required Parameters
+===================
+
+--integration-instance-id [text]
+
+Unique Integration Instance identifier.
+
+
+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
+
+--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", "--enable-dual-stack", "--enable-propagation", "--
+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/integration/integration-instance/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/integration/integration-instance/create.html#cmdoption-display-name
+       export is_byol=<substitute-value-of-is_byol> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-is-byol
+       export message_packs=<substitute-value-of-message_packs> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-message-packs
+       export type=<substitute-value-of-type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/integration/integration-instance/create.html#cmdoption-type
+
+       integration_instance_id=$(oci integration integration-instance create --compartment-id $compartment_id --display-name $display_name --is-byol $is_byol --message-packs $message_packs --type $type --query data.id --raw-output)
+
+       oci integration integration-instance disable-process-automation --integration-instance-id $integration_instance_id

oci_cli/help_text_producer/data_files/text/cmdref/integration/integration-instance.txt

@@ -24,10 +24,14 @@ Available Commands
 * change-private-endpoint-outbound-connection-private-endpoint-
   outbound-connection
 
+* convert-instance
+
 * create
 
 * delete
 
+* disable-process-automation
+
 * disaster-recovery-failover
 
 * enable-process-automation

oci_cli/help_text_producer/data_files/text/cmdref/integration.txt

@@ -27,10 +27,14 @@ Available Commands
   * change-private-endpoint-outbound-connection-private-endpoint-
     outbound-connection
 
+  * convert-instance
+
   * create
 
   * delete
 
+  * disable-process-automation
+
   * disaster-recovery-failover
 
   * enable-process-automation

oci_cli/help_text_producer/data_files/text/index.txt

@@ -62,6 +62,8 @@ Available Service Commands
 
 * Bastion (bastion)
 
+* Batch (batch)
+
 * Big Data Service (bds)
 
 * Block Volume Service (bv)

oci_cli/service_mapping.py

@@ -103,6 +103,11 @@ service_mapping = {
         "Bastion",
         "Identity & Security"
     ],
+    "batch": [
+        "batch",
+        "Batch",
+        "Others"
+    ],
     "bds": [
         "bds",
         "Big Data Service",

oci_cli/version.py

@@ -2,4 +2,4 @@
 # Copyright (c) 2016, 2021, Oracle and/or its affiliates.  All rights reserved.
 # This software is dual-licensed to you under the Universal Permissive License (UPL) 1.0 as shown at https://oss.oracle.com/licenses/upl or Apache License 2.0 as shown at http://www.apache.org/licenses/LICENSE-2.0. You may choose either license.
 
-__version__ = '3.71.1'
+__version__ = '3.71.3'

{oci_cli-3.71.1.dist-info → oci_cli-3.71.3.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: oci-cli
-Version: 3.71.1
+Version: 3.71.3
 Summary: Oracle Cloud Infrastructure CLI
 Home-page: https://docs.cloud.oracle.com/iaas/Content/API/Concepts/cliconcepts.htm
 Author: Oracle
@@ -23,7 +23,7 @@ Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Programming Language :: Python :: 3.13
 Requires-Python: >=3.6
-Requires-Dist: oci (==2.164.1)
+Requires-Dist: oci (==2.164.3)
 Requires-Dist: arrow (>=1.0.0)
 Requires-Dist: certifi (>=2025.1.31)
 Requires-Dist: click (==8.0.4)