PyPI - oci-cli - Versions diffs - 3.64.0__py3-none-any.whl → 3.65.0__py3-none-any.whl - Mend

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

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (508) hide show

oci_cli/help_text_producer/data_files/text/cmdref/dts/appliance/request-entitlement.txt DELETED Viewed

@@ -1,189 +0,0 @@
-"request-entitlement"
-*********************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Create the Entitlement to use a Transfer Appliance. It requires some
-offline process of review and signatures before request is granted.
-Usage
-=====
-   oci dts appliance request-entitlement [OPTIONS]
-Required Parameters
-===================
---compartment-id, -c [text]
-Root compartment OCID
---email [text]
-Requestor email
---name [text]
-Requestor name
-Optional Parameters
-===================
---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
-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]
---freeform-tags [complex type]
-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:
-   {"Department": "Finance"}
-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
---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 resource to reach the lifecycle state
-defined by "--wait-for-state". Defaults to 1200 seconds.
---wait-for-state [text]
-This operation creates, modifies or deletes a resource that has a
-defined lifecycle state. Specify this option to perform the action and
-then wait until the resource reaches a given lifecycle 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:
-   ACTIVE, CREATING, DELETED, INACTIVE
---wait-interval-seconds [integer]
-Check every "--wait-interval-seconds" to see whether the resource has
-reached the lifecycle 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/dts/appliance/request-entitlement.html#cmdoption-compartment-id
-       export email=<substitute-value-of-email> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request-entitlement.html#cmdoption-email
-       export name=<substitute-value-of-name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request-entitlement.html#cmdoption-name
-       oci dts appliance request-entitlement --compartment-id $compartment_id --email $email --name $name

oci_cli/help_text_producer/data_files/text/cmdref/dts/appliance/request-return-label.txt DELETED Viewed

@@ -1,249 +0,0 @@
-"request-return-label"
-**********************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-Description
-===========
-Request return label
-Usage
-=====
-   oci dts appliance request-return-label [OPTIONS]
-Required Parameters
-===================
---appliance-label [text]
-Appliance label
---job-id [text]
-OCID of the Transfer Job
---pickup-window-end-time [datetime]
-End time for the window to pickup the device,
-   The following datetime formats are supported:
-UTC with microseconds
----------------------
-   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
-   Example: 2017-09-15T20:30:00.123456Z
-   UTC with milliseconds
-   ***********************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
-       Example: 2017-09-15T20:30:00.123Z
-   UTC without milliseconds
-   **************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T20:30:00Z
-   UTC with minute precision
-   **************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T20:30Z
-Timezone with microseconds
---------------------------
-   Format: YYYY-MM-DDTHH:mm:ssTZD
-   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
-   Timezone with milliseconds
-   ***************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
-   Timezone without milliseconds
-   *******************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
-   Timezone with minute precision
-   *******************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
-   Short date and time
-   ********************
-   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
-   .. code::
-       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
-       Example: '2017-09-15 17:25'
-   Date Only
-   **********
-   This date will be taken as midnight UTC of that day
-   .. code::
-       Format: YYYY-MM-DD
-       Example: 2017-09-15
-   Epoch seconds
-   **************
-   .. code::
-       Example: 1412195400
---pickup-window-start-time [datetime]
-Start time for the window to pickup the device,
-   The following datetime formats are supported:
-UTC with microseconds
----------------------
-   Format: YYYY-MM-DDTHH:mm:ss.ssssssTZD
-   Example: 2017-09-15T20:30:00.123456Z
-   UTC with milliseconds
-   ***********************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ss.sssTZD
-       Example: 2017-09-15T20:30:00.123Z
-   UTC without milliseconds
-   **************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T20:30:00Z
-   UTC with minute precision
-   **************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T20:30Z
-Timezone with microseconds
---------------------------
-   Format: YYYY-MM-DDTHH:mm:ssTZD
-   Example: 2017-09-15T12:30:00.456789-08:00, 2017-09-15T12:30:00.456789-0800
-   Timezone with milliseconds
-   ***************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00.456-08:00, 2017-09-15T12:30:00.456-0800
-   Timezone without milliseconds
-   *******************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mm:ssTZD
-       Example: 2017-09-15T12:30:00-08:00, 2017-09-15T12:30:00-0800
-   Timezone with minute precision
-   *******************************
-   .. code::
-       Format: YYYY-MM-DDTHH:mmTZD
-       Example: 2017-09-15T12:30-08:00, 2017-09-15T12:30-0800
-   Short date and time
-   ********************
-   The timezone for this date and time will be taken as UTC (Needs to be surrounded by single or double quotes)
-   .. code::
-       Format: 'YYYY-MM-DD HH:mm' or "YYYY-MM-DD HH:mm"
-       Example: '2017-09-15 17:25'
-   Date Only
-   **********
-   This date will be taken as midnight UTC of that day
-   .. code::
-       Format: YYYY-MM-DD
-       Example: 2017-09-15
-   Epoch seconds
-   **************
-   .. code::
-       Example: 1412195400
-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
-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"

oci_cli/help_text_producer/data_files/text/cmdref/dts/appliance/request.txt DELETED Viewed

@@ -1,188 +0,0 @@
-"request"
-*********
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Create a new Transfer Appliance
-Usage
-=====
-   oci dts appliance request [OPTIONS]
-Required Parameters
-===================
---address1 [text]
-Address line 1.
---addressee [text]
-Company or person to send the appliance to
---care-of [text]
-Place/person to direct the package to.
---city-or-locality [text]
-City or Locality.
---country [text]
-Country.
---email [text]
-Email address.
---job-id [text]
-OCID of the Transfer Job
---phone-number [text]
-Phone number.
---state-province-region [text]
-State or Province or Region.
---zip-postal-code [text]
-Zip or Postal Code
-Optional Parameters
-===================
---address2 [text]
-Optional address line 2.
---address3 [text]
-Optional address line 3.
---address4 [text]
-Optional address line 4.
---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 resource to reach the lifecycle state
-defined by "--wait-for-state". Defaults to 1200 seconds.
---minimum-storage-capacity-in-terabytes [integer]
-Minimum storage capacity of the device, in terabytes. Valid options
-are 50, 95 and 150.
---setup-notifications
-Setup notifications for the transfer appliance
---wait-for-state [text]
-This operation creates, modifies or deletes a resource that has a
-defined lifecycle state. Specify this option to perform the action and
-then wait until the resource reaches a given lifecycle 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:
-   CANCELLED, COMPLETE, CUSTOMER_LOST, CUSTOMER_NEVER_RECEIVED, DELETED, DELIVERED, ERROR, FINALIZED, ORACLE_NEVER_RECEIVED, ORACLE_PREPARING, ORACLE_RECEIVED, ORACLE_RECEIVED_CANCELLED, PREPARING, PROCESSING, REJECTED, REQUESTED, RETURN_DELAYED, RETURN_SHIPPED, RETURN_SHIPPED_CANCELLED, SHIPPING
---wait-interval-seconds [integer]
-Check every "--wait-interval-seconds" to see whether the resource has
-reached the lifecycle 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 bucket=<substitute-value-of-bucket> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/job/create.html#cmdoption-bucket
-       export compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/job/create.html#cmdoption-compartment-id
-       export device_type=<substitute-value-of-device_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/job/create.html#cmdoption-device-type
-       export display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/job/create.html#cmdoption-display-name
-       export address1=<substitute-value-of-address1> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-address1
-       export addressee=<substitute-value-of-addressee> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-addressee
-       export care_of=<substitute-value-of-care_of> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-care-of
-       export city_or_locality=<substitute-value-of-city_or_locality> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-city-or-locality
-       export country=<substitute-value-of-country> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-country
-       export email=<substitute-value-of-email> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-email
-       export phone_number=<substitute-value-of-phone_number> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-phone-number
-       export state_province_region=<substitute-value-of-state_province_region> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-state-province-region
-       export zip_postal_code=<substitute-value-of-zip_postal_code> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/request.html#cmdoption-zip-postal-code
-       job_id=$(oci dts job create --bucket $bucket --compartment-id $compartment_id --device-type $device_type --display-name $display_name --query data.id --raw-output)
-       oci dts appliance request --address1 $address1 --addressee $addressee --care-of $care_of --city-or-locality $city_or_locality --country $country --email $email --job-id $job_id --phone-number $phone_number --state-province-region $state_province_region --zip-postal-code $zip_postal_code

oci_cli/help_text_producer/data_files/text/cmdref/dts/appliance/setup-notifications.txt DELETED Viewed

@@ -1,63 +0,0 @@
-"setup-notifications"
-*********************
-* Description
-* Usage
-* Required Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Setup notifications for appliance import
-Usage
-=====
-   oci dts appliance setup-notifications [OPTIONS]
-Required Parameters
-===================
---appliance-label [text]
-Appliance Label
-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 appliance_label=<substitute-value-of-appliance_label> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/dts/appliance/setup-notifications.html#cmdoption-appliance-label
-       oci dts appliance setup-notifications --appliance-label $appliance_label

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

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