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

oci-cli 3.64.1py3-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 (478) hide show

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

@@ -1,144 +0,0 @@
-"list"
-******
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Returns a list of all Software Sources.
-Usage
-=====
-   oci os-management software-source 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
---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.
---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/software-source/list.html#cmdoption-compartment-id
-       oci os-management software-source list --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/software-source/remove-packages.txt DELETED Viewed

@@ -1,112 +0,0 @@
-"remove-packages"
-*****************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Removes a given list of Software Packages from a specific Software
-Source.
-Usage
-=====
-   oci os-management software-source remove-packages [OPTIONS]
-Required Parameters
-===================
---package-names [complex type]
-the list of package names 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.
---software-source-id [text]
-The OCID of the software source.
-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 and paste the following example into a JSON file, replacing the
-example parameters with your own.
-       oci os-management software-source remove-packages --generate-param-json-input package-names > package-names.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 arch_type=<substitute-value-of-arch_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/software-source/create.html#cmdoption-arch-type
-       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/software-source/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/software-source/create.html#cmdoption-display-name
-       software_source_id=$(oci os-management software-source create --arch-type $arch_type --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
-       oci os-management software-source remove-packages --package-names file://package-names.json --software-source-id $software_source_id

oci_cli/help_text_producer/data_files/text/cmdref/os-management/software-source/search-packages.txt DELETED Viewed

@@ -1,124 +0,0 @@
-"search-packages"
-*****************
-* Description
-* Usage
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Searches all of the available Software Sources and returns any/all
-Software Packages matching the search criteria.
-Usage
-=====
-   oci os-management software-source search-packages [OPTIONS]
-Optional Parameters
-===================
---cve-name [text]
-The name of the CVE as published. Example: *CVE-2006-4535*
---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.
---package-name [text]
-Name of package for which to search. This should be the full package
-name including version and architecture
---page [text]
-The page token representing the page at which to start retrieving
-results. This is usually retrieved from a previous list call.
---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.
-       oci os-management software-source search-packages

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

@@ -1,187 +0,0 @@
-"update"
-********
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Updates an existing custom Software Source on the management system.
-Usage
-=====
-   oci os-management software-source update [OPTIONS]
-Required Parameters
-===================
---software-source-id [text]
-The OCID of the software source.
-Optional Parameters
-===================
---checksum-type [text]
-The yum repository checksum type used by this software source
-Accepted values are:
-   SHA1, SHA256, SHA384, SHA512
---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]
-Information specified by the user about the software source
---display-name [text]
-User friendly name for the software source
---force
-Perform update without prompting for confirmation.
---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
---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.
---maintainer-email [text]
-Email address of the person maintaining this software source
---maintainer-name [text]
-Name of the person maintaining this software source
---maintainer-phone [text]
-Phone number of the person maintaining this software source
---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 arch_type=<substitute-value-of-arch_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/os-management/software-source/create.html#cmdoption-arch-type
-       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/software-source/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/software-source/create.html#cmdoption-display-name
-       software_source_id=$(oci os-management software-source create --arch-type $arch_type --compartment-id $compartment_id --display-name $display_name --query data.id --raw-output)
-       oci os-management software-source update --software-source-id $software_source_id

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

@@ -1,34 +0,0 @@
-software-source
-***************
-Description
-===========
-A software source contains a collection of packages
-Available Commands
-==================
-* add-packages
-* change-compartment
-* create
-* delete
-* get
-* get-package
-* list
-* list-packages
-* remove-packages
-* search-packages
-* update

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

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