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/service-mesh/virtual-deployment/update-virtual-deployment-disabled-service-discovery-configuration.txt DELETED Viewed

@@ -1,204 +0,0 @@
-"update-virtual-deployment-disabled-service-discovery-configuration"
-********************************************************************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Updates the VirtualDeployment.
-Usage
-=====
-   oci service-mesh virtual-deployment update-virtual-deployment-disabled-service-discovery-configuration [OPTIONS]
-Required Parameters
-===================
---virtual-deployment-id [text]
-Unique VirtualDeployment identifier.
-Optional Parameters
-===================
---access-logging [complex type]
-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.
---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
---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.
---listeners [complex type]
-The listeners for the virtual deployment.
-This option is a JSON list with items of type
-VirtualDeploymentListener.  For documentation on
-VirtualDeploymentListener please see our API reference: https://docs.
-cloud.oracle.com/api/#/en/servicemesh/20220615/datatypes/VirtualDeplo
-ymentListener. 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.
---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
-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)
-       virtual_service_id=$(oci service-mesh virtual-service create --compartment-id $compartment_id --mesh-id $mesh_id --name $name --query data.id --raw-output)
-       virtual_deployment_id=$(oci service-mesh virtual-deployment create --compartment-id $compartment_id --name $name --virtual-service-id $virtual_service_id --query data.id --raw-output)
-       oci service-mesh virtual-deployment update-virtual-deployment-disabled-service-discovery-configuration --virtual-deployment-id $virtual_deployment_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-deployment/update-virtual-deployment-dns-service-discovery-configuration.txt DELETED Viewed

@@ -1,209 +0,0 @@
-"update-virtual-deployment-dns-service-discovery-configuration"
-***************************************************************
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Updates the VirtualDeployment.
-Usage
-=====
-   oci service-mesh virtual-deployment update-virtual-deployment-dns-service-discovery-configuration [OPTIONS]
-Required Parameters
-===================
---service-discovery-hostname [text]
-The hostname of the virtual deployments.
---virtual-deployment-id [text]
-Unique VirtualDeployment identifier.
-Optional Parameters
-===================
---access-logging [complex type]
-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.
---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
---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.
---listeners [complex type]
-The listeners for the virtual deployment.
-This option is a JSON list with items of type
-VirtualDeploymentListener.  For documentation on
-VirtualDeploymentListener please see our API reference: https://docs.
-cloud.oracle.com/api/#/en/servicemesh/20220615/datatypes/VirtualDeplo
-ymentListener. 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.
---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
-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
-       export service_discovery_hostname=<substitute-value-of-service_discovery_hostname> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/service-mesh/virtual-deployment/update-virtual-deployment-dns-service-discovery-configuration.html#cmdoption-service-discovery-hostname
-       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)
-       virtual_service_id=$(oci service-mesh virtual-service create --compartment-id $compartment_id --mesh-id $mesh_id --name $name --query data.id --raw-output)
-       virtual_deployment_id=$(oci service-mesh virtual-deployment create --compartment-id $compartment_id --name $name --virtual-service-id $virtual_service_id --query data.id --raw-output)
-       oci service-mesh virtual-deployment update-virtual-deployment-dns-service-discovery-configuration --service-discovery-hostname $service_discovery_hostname --virtual-deployment-id $virtual_deployment_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-deployment/update.txt DELETED Viewed

@@ -1,215 +0,0 @@
-"update"
-********
-* Description
-* Usage
-* Required Parameters
-* Optional Parameters
-* Global Parameters
-* Example using required parameter
-Description
-===========
-Updates the VirtualDeployment.
-Usage
-=====
-   oci service-mesh virtual-deployment update [OPTIONS]
-Required Parameters
-===================
---virtual-deployment-id [text]
-Unique VirtualDeployment identifier.
-Optional Parameters
-===================
---access-logging [complex type]
-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.
---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
---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.
---listeners [complex type]
-The listeners for the virtual deployment.
-This option is a JSON list with items of type
-VirtualDeploymentListener.  For documentation on
-VirtualDeploymentListener please see our API reference: https://docs.
-cloud.oracle.com/api/#/en/servicemesh/20220615/datatypes/VirtualDeplo
-ymentListener. 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.
---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.
---service-discovery [complex type]
-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.
---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
-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)
-       virtual_service_id=$(oci service-mesh virtual-service create --compartment-id $compartment_id --mesh-id $mesh_id --name $name --query data.id --raw-output)
-       virtual_deployment_id=$(oci service-mesh virtual-deployment create --compartment-id $compartment_id --name $name --virtual-service-id $virtual_service_id --query data.id --raw-output)
-       oci service-mesh virtual-deployment update --virtual-deployment-id $virtual_deployment_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-deployment.txt DELETED Viewed

@@ -1,33 +0,0 @@
-virtual-deployment
-******************
-Description
-===========
-This resource represents a customer-managed virtual service deployment
-in the Service Mesh.
-Available Commands
-==================
-* change-compartment
-* create
-* create-virtual-deployment-disabled-service-discovery-configuration
-* create-virtual-deployment-dns-service-discovery-configuration
-* delete
-* get
-* list
-* update
-* update-virtual-deployment-disabled-service-discovery-configuration
-* update-virtual-deployment-dns-service-discovery-configuration

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