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/service-mesh/virtual-service-route-table/get.txt

@@ -1,105 +0,0 @@
-"get"
-*****
-
-* Description
-
-* Usage
-
-* Required Parameters
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Gets a VirtualServiceRouteTable by identifier.
-
-
-Usage
-=====
-
-   oci service-mesh virtual-service-route-table get [OPTIONS]
-
-
-Required Parameters
-===================
-
---virtual-service-route-table-id [text]
-
-Unique VirtualServiceRouteTable identifier.
-
-
-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 service-mesh mesh create --generate-param-json-input certificate-authorities > certificate-authorities.json
-
-       oci service-mesh virtual-service-route-table create --generate-param-json-input route-rules > route-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)
-
-       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_service_route_table_id=$(oci service-mesh virtual-service-route-table create --compartment-id $compartment_id --name $name --route-rules file://route-rules.json --virtual-service-id $virtual_service_id --query data.id --raw-output)
-
-       oci service-mesh virtual-service-route-table get --virtual-service-route-table-id $virtual_service_route_table_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-service-route-table/list.txt

@@ -1,150 +0,0 @@
-"list"
-******
-
-* Description
-
-* Usage
-
-* Required Parameters
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Returns a list of VirtualServiceRouteTable objects.
-
-
-Usage
-=====
-
-   oci service-mesh virtual-service-route-table 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.
-
---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
-
---id [text]
-
-Unique VirtualServiceRouteTable identifier.
-
---lifecycle-state [text]
-
-A filter to return only resources that match the life cycle state
-given.
-
-Accepted values are:
-
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
-
---limit [integer]
-
-The maximum number of items to return.
-
---name [text]
-
-A filter to return only resources that match the entire name given.
-
---page [text]
-
-A token representing the position at which to start retrieving
-results. This must come from the *opc-next-page* header field of a
-previous response.
-
---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 ‘name’ is
-ascending.
-
-Accepted values are:
-
-   id, name, timeCreated
-
---sort-order [text]
-
-The sort order to use, either ‘ASC’ or ‘DESC’.
-
-Accepted values are:
-
-   ASC, DESC
-
---virtual-service-id [text]
-
-Unique VirtualService identifier.
-
-
-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/service-mesh/virtual-service-route-table/list.html#cmdoption-compartment-id
-
-       oci service-mesh virtual-service-route-table list --compartment-id $compartment_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-service-route-table/update.txt

@@ -1,201 +0,0 @@
-"update"
-********
-
-* Description
-
-* Usage
-
-* Required Parameters
-
-* Optional Parameters
-
-* Global Parameters
-
-* Example using required parameter
-
-
-Description
-===========
-
-Updates the VirtualServiceRouteTable.
-
-
-Usage
-=====
-
-   oci service-mesh virtual-service-route-table update [OPTIONS]
-
-
-Required Parameters
-===================
-
---virtual-service-route-table-id [text]
-
-Unique VirtualServiceRouteTable identifier.
-
-
-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
-
---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.
-
---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.
-
---priority [integer]
-
-The priority of the route table. Lower value means higher priority.
-The routes are declared based on the priority.
-
---route-rules [complex type]
-
-The route rules for the virtual service.
-
-This option is a JSON list with items of type
-VirtualServiceTrafficRouteRuleDetails.  For documentation on
-VirtualServiceTrafficRouteRuleDetails please see our API reference: h
-ttps://docs.cloud.oracle.com/api/#/en/servicemesh/20220615/datatypes/
-VirtualServiceTrafficRouteRuleDetails. 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
-
-       oci service-mesh virtual-service-route-table create --generate-param-json-input route-rules > route-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)
-
-       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_service_route_table_id=$(oci service-mesh virtual-service-route-table create --compartment-id $compartment_id --name $name --route-rules file://route-rules.json --virtual-service-id $virtual_service_id --query data.id --raw-output)
-
-       oci service-mesh virtual-service-route-table update --virtual-service-route-table-id $virtual_service_route_table_id

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/virtual-service-route-table.txt

@@ -1,25 +0,0 @@
-virtual-service-route-table
-***************************
-
-
-Description
-===========
-
-This resource represents a customer-managed service route table in the
-Service Mesh.
-
-
-Available Commands
-==================
-
-* change-compartment
-
-* create
-
-* delete
-
-* get
-
-* list
-
-* update

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

@@ -1,27 +0,0 @@
-virtual-service
-***************
-
-
-Description
-===========
-
-This resource represents a customer-managed service in the Service
-Mesh. Each virtual service declares multiple running versions of the
-service and maps to a group of instances/pods running a specific
-version of the actual service.
-
-
-Available Commands
-==================
-
-* change-compartment
-
-* create
-
-* delete
-
-* get
-
-* list
-
-* update

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh/work-request.txt

@@ -1,22 +0,0 @@
-work-request
-************
-
-
-Description
-===========
-
-A description of the work request status.
-
-
-Available Commands
-==================
-
-* cancel
-
-* get
-
-* list
-
-* list-work-request-errors
-
-* list-work-request-logs

oci_cli/help_text_producer/data_files/text/cmdref/service-mesh.txt

@@ -1,139 +0,0 @@
-service-mesh
-************
-
-
-Description
-===========
-
-Use the Service Mesh CLI to manage mesh, virtual service, access
-policy and other mesh related items.
-
-
-Available Commands
-==================
-
-* access-policy
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* debug
-
-  * report
-
-* ingress-gateway
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* ingress-gateway-route-table
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* mesh
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* proxy-details
-
-  * get
-
-* virtual-deployment
-
-  * 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
-
-* virtual-service
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* virtual-service-route-table
-
-  * change-compartment
-
-  * create
-
-  * delete
-
-  * get
-
-  * list
-
-  * update
-
-* work-request
-
-  * cancel
-
-  * get
-
-  * list
-
-  * list-work-request-errors
-
-  * list-work-request-logs