PyPI - oci-cli - Versions diffs - 3.64.1__py3-none-any.whl → 3.65.1__py3-none-any.whl - Mend

oci-cli 3.64.1py3-none-any.whl → 3.65.1py3-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 (572) hide show

oci_cli/help_text_producer/data_files/text/cmdref/os-management/work-request/list.txt DELETED Viewed

@@ -1,148 +0,0 @@
-"list"
-******
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Lists the work requests in a compartment.
-Usage
-=====
-   oci os-management work-request 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
---limit [integer]
-The maximum number of items to return.
---managed-instance-id [text]
-The ID of the managed instance for which to list resources.
---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/work-request/list.html#cmdoption-compartment-id
-       oci os-management work-request list --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/work-request.txt DELETED Viewed

@@ -1,20 +0,0 @@
-work-request
-************
-Description
-===========
-A description of workrequest status
-Available Commands
-==================
-* get
-* list
-* list-errors
-* list-logs

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

@@ -1,187 +0,0 @@
-os-management
-*************
-Description
-===========
-CLI for the OS Management service. Use these CLI operations for
-working with Managed instances and Managed instance groups.
-Available Commands
-==================
-* erratum
-  * get
-* erratum-summary
-  * list-errata
-* event
-  * delete-content
-  * get-content
-  * get-report
-  * list
-  * list-related-events
-  * update
-  * upload-content
-* managed-instance
-  * attach-child
-  * attach-parent
-  * detach-child
-  * detach-parent
-  * disable-module-stream
-  * enable-module-stream
-  * get
-  * install-all-updates
-  * install-all-windows-updates
-  * install-module-profile
-  * install-package
-  * install-update
-  * install-windows-update
-  * list
-  * list-available-packages
-  * list-available-software-sources
-  * list-available-updates
-  * list-available-windows-updates
-  * list-installed-packages
-  * list-installed-windows-updates
-  * list-managed-instance-errata
-  * list-module-profiles
-  * list-module-streams
-  * remove-module-profile
-  * remove-package
-  * switch-module-stream
-* managed-instance-group
-  * attach
-  * change-compartment
-  * create
-  * delete
-  * detach
-  * get
-  * install-all-updates
-  * list
-  * update
-* module-profile
-  * get
-  * list
-* module-stream
-  * get
-  * list
-* scheduled-job
-  * change-compartment
-  * create
-  * delete
-  * get
-  * list
-  * list-upcoming
-  * run-now
-  * skip-next-execution
-  * update
-* software-source
-  * add-packages
-  * change-compartment
-  * create
-  * delete
-  * get
-  * get-package
-  * list
-  * list-packages
-  * remove-packages
-  * search-packages
-  * update
-* update-managed-instance-details
-  * update-managed-instance
-* windows-update
-  * get
-  * list
-* work-request
-  * get
-  * list
-  * list-errors
-  * list-logs

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/access-policy/change-compartment.txt DELETED Viewed

@@ -1,143 +0,0 @@
-"change-compartment"
-********************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Moves an AccessPolicy resource from one compartment identifier to
-another. When provided, If-Match is checked against ETag values of the
-resource.
-Usage
-=====
-   oci service-mesh access-policy change-compartment [OPTIONS]
-Required Parameters
-===================
---access-policy-id [text]
-Unique AccessPolicy identifier.
---compartment-id, -c [text]
-The OCID of the compartment.
-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, 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 service-mesh mesh create --generate-param-json-input certificate-authorities > certificate-authorities.json
-       oci service-mesh access-policy create --generate-param-json-input rules > rules.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/service-mesh/mesh/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/service-mesh/mesh/create.html#cmdoption-display-name
-       mesh_id=$(oci service-mesh mesh create --certificate-authorities file://certificate-authorities.json --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
-       access_policy_id=$(oci service-mesh access-policy create --compartment-id $compartment_id --mesh-id $mesh_id --name $name --rules file://rules.json --query data.id --raw-output)
-       oci service-mesh access-policy change-compartment --access-policy-id $access_policy_id --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/access-policy/create.txt DELETED Viewed

@@ -1,187 +0,0 @@
-"create"
-********
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Creates a new AccessPolicy.
-Usage
-=====
-   oci service-mesh access-policy create [OPTIONS]
-Required Parameters
-===================
---compartment-id, -c [text]
-The OCID of the compartment.
---mesh-id [text]
-The OCID of the service mesh in which this access policy is created.
---name [text]
-A user-friendly name. The name has to be unique within the same
-service mesh and cannot be changed after creation. Avoid entering
-confidential information.
-Example:
-   My unique resource name
---rules [complex type]
-List of applicable rules 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
-===================
---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.
---description [text]
-Description of the resource. It can be changed after creation. Avoid
-entering confidential information.
-Example:
-   This is my new resource
---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 service-mesh mesh create --generate-param-json-input certificate-authorities > certificate-authorities.json
-       oci service-mesh access-policy create --generate-param-json-input rules > rules.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/service-mesh/mesh/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/service-mesh/mesh/create.html#cmdoption-display-name
-       mesh_id=$(oci service-mesh mesh create --certificate-authorities file://certificate-authorities.json --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
-       oci service-mesh access-policy create --compartment-id $compartment_id --mesh-id $mesh_id --name $name --rules file://rules.json

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

oci-cli 3.64.1py3-none-any.whl → 3.65.1py3-none-any.whl