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/os-management/scheduled-job/delete.txt DELETED Viewed

@@ -1,135 +0,0 @@
-"delete"
-********
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Cancels an existing Scheduled Job on the management system
-Usage
-=====
-   oci os-management scheduled-job delete [OPTIONS]
-Required Parameters
-===================
---scheduled-job-id [text]
-The ID of the scheduled job.
-Optional Parameters
-===================
---force
-Perform deletion without prompting for confirmation.
---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 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, DELETING, FAILED, UPDATING
---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/os-management/scheduled-job/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/os-management/scheduled-job/create.html#cmdoption-display-name
-       export operation_type=<substitute-value-of-operation_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-operation-type
-       export schedule_type=<substitute-value-of-schedule_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-schedule-type
-       export time_next_execution=<substitute-value-of-time_next_execution> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-time-next-execution
-       scheduled_job_id=$(oci os-management scheduled-job create --compartment-id $compartment_id --display-name $display_name --operation-type $operation_type --schedule-type $schedule_type --time-next-execution $time_next_execution --query data.id --raw-output)
-       oci os-management scheduled-job delete --scheduled-job-id $scheduled_job_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/scheduled-job/get.txt DELETED Viewed

@@ -1,97 +0,0 @@
-"get"
-*****
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Gets the detailed information for the Scheduled Job with the given ID.
-Usage
-=====
-   oci os-management scheduled-job get [OPTIONS]
-Required Parameters
-===================
---scheduled-job-id [text]
-The ID of the scheduled job.
-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"
-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/os-management/scheduled-job/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/os-management/scheduled-job/create.html#cmdoption-display-name
-       export operation_type=<substitute-value-of-operation_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-operation-type
-       export schedule_type=<substitute-value-of-schedule_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-schedule-type
-       export time_next_execution=<substitute-value-of-time_next_execution> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/create.html#cmdoption-time-next-execution
-       scheduled_job_id=$(oci os-management scheduled-job create --compartment-id $compartment_id --display-name $display_name --operation-type $operation_type --schedule-type $schedule_type --time-next-execution $time_next_execution --query data.id --raw-output)
-       oci os-management scheduled-job get --scheduled-job-id $scheduled_job_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/scheduled-job/list-upcoming.txt DELETED Viewed

@@ -1,251 +0,0 @@
-"list-upcoming"
-***************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Returns a list of all of the Scheduled Jobs whose next execution time
-is at or before the specified time.
-Usage
-=====
-   oci os-management scheduled-job list-upcoming [OPTIONS]
-Required Parameters
-===================
---compartment-id, -c [text]
-The ID of the compartment in which to list resources.
---time-end [datetime]
-The cut-off time before which to list all upcoming schedules, in ISO
-8601 format
-Example: 2017-07-14T02:40:00.000Z
-   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
-===================
---all
-Fetches all pages of results. If you provide this option, then you
-cannot provide the "--limit" option.
---display-name [text]
-A user-friendly name. Does not have to be unique, and it’s changeable.
-Example:
-   My new resource
---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
---lifecycle-state [text]
-The current lifecycle state for the object.
-Accepted values are:
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
---limit [integer]
-The maximum number of items to return.
---os-family [text]
-The OS family for which to list resources.
-Accepted values are:
-   ALL, LINUX, WINDOWS
---page [text]
-The page token representing the page at which to start retrieving
-results. This is usually retrieved from a previous list call.
---page-size [integer]
-When fetching results, the number of results to fetch per call. Only
-valid when used with "--all" or "--limit", and ignored otherwise.
---sort-by [text]
-The field to sort by. Only one sort order may be provided. Default
-order for TIMECREATED is descending. Default order for DISPLAYNAME is
-ascending. If no value is specified TIMECREATED is default.
-Accepted values are:
-   DISPLAYNAME, TIMECREATED
---sort-order [text]
-The sort order to use, either ‘asc’ or ‘desc’.
-Accepted values are:
-   ASC, DESC
---tag-name [text]
-The name of the tag.
---tag-value [text]
-The value for the tag.
-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/os-management/scheduled-job/list-upcoming.html#cmdoption-compartment-id
-       export time_end=<substitute-value-of-time_end> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/scheduled-job/list-upcoming.html#cmdoption-time-end
-       oci os-management scheduled-job list-upcoming --compartment-id $compartment_id --time-end $time_end

oci_cli/help_text_producer/data_files/text/cmdref/os-management/scheduled-job/list.txt DELETED Viewed

@@ -1,174 +0,0 @@
-"list"
-******
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Returns a list of all of the currently active Scheduled Jobs in the
-system
-Usage
-=====
-   oci os-management scheduled-job list [OPTIONS]
-Required Parameters
-===================
---compartment-id, -c [text]
-The ID of the compartment in which to list resources.
-Optional Parameters
-===================
---all
-Fetches all pages of results. If you provide this option, then you
-cannot provide the "--limit" option.
---display-name [text]
-A user-friendly name. Does not have to be unique, and it’s changeable.
-Example:
-   My new resource
---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
---is-restricted [boolean]
-If true, will only filter out restricted Autonomous Linux Scheduled
-Job
---lifecycle-state [text]
-The current lifecycle state for the object.
-Accepted values are:
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
---limit [integer]
-The maximum number of items to return.
---managed-instance-group-id [text]
-The ID of the managed instace group for which to list resources.
---managed-instance-id [text]
-The ID of the managed instance for which to list resources.
---operation-type [text]
-The operation type for which to list resources
-Accepted values are:
-   COMPOUND, DISABLEMODULESTREAM, ENABLEMODULESTREAM, INSTALL, INSTALLMODULESTREAMPROFILE, REMOVE, REMOVEMODULESTREAMPROFILE, SWITCHMODULESTREAM, UPDATE, UPDATEALL
---os-family [text]
-The OS family for which to list resources.
-Accepted values are:
-   ALL, LINUX, WINDOWS
---page [text]
-The page token representing the page at which to start retrieving
-results. This is usually retrieved from a previous list call.
---page-size [integer]
-When fetching results, the number of results to fetch per call. Only
-valid when used with "--all" or "--limit", and ignored otherwise.
---sort-by [text]
-The field to sort by. Only one sort order may be provided. Default
-order for TIMECREATED is descending. Default order for DISPLAYNAME is
-ascending. If no value is specified TIMECREATED is default.
-Accepted values are:
-   DISPLAYNAME, TIMECREATED
---sort-order [text]
-The sort order to use, either ‘asc’ or ‘desc’.
-Accepted values are:
-   ASC, DESC
-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/os-management/scheduled-job/list.html#cmdoption-compartment-id
-       oci os-management scheduled-job list --compartment-id $compartment_id

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