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

oci_cli/help_text_producer/data_files/text/cmdref/os-management/erratum-summary/list-errata.txt

@@ -1,310 +0,0 @@
-"list-errata"
-*************
-
-* Description
-
-* Usage
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Returns a list of all of the currently available Errata in the system
-
-
-Usage
-=====
-
-   oci os-management erratum-summary list-errata [OPTIONS]
-
-
-Optional Parameters
-===================
-
---advisory-name [text]
-
-The assigned erratum name. It’s unique and not changeable.
-
-Example:
-
-   ELSA-2020-5804
-
---all
-
-Fetches all pages of results. If you provide this option, then you
-cannot provide the "--limit" option.
-
---compartment-id, -c [text]
-
-The ID of the compartment in which to list resources. This parameter
-is optional and in some cases may have no effect.
-
---erratum-id [text]
-
-The OCID of the erratum.
-
---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.
-
---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 errata by. Only one sort order may be provided.
-Default order for ISSUEDATE is descending. Default order for
-ADVISORYNAME is ascending. If no value is specified ISSUEDATE is
-default.
-
-Accepted values are:
-
-   ADVISORYNAME, ISSUEDATE
-
---sort-order [text]
-
-The sort order to use, either ‘asc’ or ‘desc’.
-
-Accepted values are:
-
-   ASC, DESC
-
---time-issue-date-end [datetime]
-
-The issue date before which to list all errata, 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
-
---time-issue-date-start [datetime]
-
-The issue date after which to list all errata, 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
-
-
-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.
-
-       oci os-management erratum-summary list-errata

oci_cli/help_text_producer/data_files/text/cmdref/os-management/erratum-summary.txt

@@ -1,15 +0,0 @@
-erratum-summary
-***************
-
-
-Description
-===========
-
-Important changes for software. This can include security |
-advisories, bug fixes, or enhancements.
-
-
-Available Commands
-==================
-
-* list-errata

oci_cli/help_text_producer/data_files/text/cmdref/os-management/erratum.txt

@@ -1,14 +0,0 @@
-erratum
-*******
-
-
-Description
-===========
-
-Details about the erratum.
-
-
-Available Commands
-==================
-
-* get

oci_cli/help_text_producer/data_files/text/cmdref/os-management/event/delete-content.txt

@@ -1,113 +0,0 @@
-"delete-content"
-****************
-
-* Description
-
-* Usage
-
-* Required Parameters
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Delete an event content ZIP archive from the service
-
-
-Usage
-=====
-
-   oci os-management event delete-content [OPTIONS]
-
-
-Required Parameters
-===================
-
---compartment-id, -c [text]
-
-The ID of the compartment in which to list resources.
-
---event-id [text]
-
-Unique Event identifier (OCID)
-
---managed-instance-id [text]
-
-Instance Oracle Cloud identifier (ocid)
-
-
-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.
-
-
-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/event/delete-content.html#cmdoption-compartment-id
-       export event_id=<substitute-value-of-event_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/event/delete-content.html#cmdoption-event-id
-       export managed_instance_id=<substitute-value-of-managed_instance_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/event/delete-content.html#cmdoption-managed-instance-id
-
-       oci os-management event delete-content --compartment-id $compartment_id --event-id $event_id --managed-instance-id $managed_instance_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/event/get-content.txt

@@ -1,108 +0,0 @@
-"get-content"
-*************
-
-* Description
-
-* Usage
-
-* Required Parameters
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Get additional data about a event as a ZIP archive. The archive
-content depends on the event eventType.
-
-
-Usage
-=====
-
-   oci os-management event get-content [OPTIONS]
-
-
-Required Parameters
-===================
-
---compartment-id, -c [text]
-
-The ID of the compartment in which to list resources.
-
---event-id [text]
-
-Unique Event identifier (OCID)
-
---file [filename]
-
-The name of the file that will receive the response data, or ‘-‘ to
-write to STDOUT.
-
---managed-instance-id [text]
-
-Instance Oracle Cloud identifier (ocid)
-
-
-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/event/get-content.html#cmdoption-compartment-id
-       export event_id=<substitute-value-of-event_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/event/get-content.html#cmdoption-event-id
-       export file=<substitute-value-of-file> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/event/get-content.html#cmdoption-file
-       export managed_instance_id=<substitute-value-of-managed_instance_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/event/get-content.html#cmdoption-managed-instance-id
-
-       oci os-management event get-content --compartment-id $compartment_id --event-id $event_id --file $file --managed-instance-id $managed_instance_id