oci-cli 3.62.2__py3-none-any.whl → 3.63.0__py3-none-any.whl

oci_cli/help_text_producer/data_files/text/cmdref/database-management/cloud-db-system-connector/check-cloud-db-system-connector-connection-status.txt

@@ -0,0 +1,133 @@
+"check-cloud-db-system-connector-connection-status"
+***************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Checks the status of the cloud DB system component connection
+specified in this connector. This operation will refresh the
+connectionStatus and timeConnectionStatusLastUpdated fields.
+
+
+Usage
+=====
+
+   oci database-management cloud-db-system-connector check-cloud-db-system-connector-connection-status [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cloud-db-system-connector-id [text]
+
+The OCID of the cloud connector.
+
+
+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 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, INACTIVE, NOT_CONNECTED, 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-compartment-id
+       export db_system_discovery_id=<substitute-value-of-db_system_discovery_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-db-system-discovery-id
+       export connector_type=<substitute-value-of-connector_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system-connector/create.html#cmdoption-connector-type
+
+       cloud_db_system_id=$(oci database-management cloud-db-system create --compartment-id $compartment_id --db-system-discovery-id $db_system_discovery_id --query data.id --raw-output)
+
+       cloud_db_system_connector_id=$(oci database-management cloud-db-system-connector create --cloud-db-system-id $cloud_db_system_id --connector-type $connector_type --query data.id --raw-output)
+
+       oci database-management cloud-db-system-connector check-cloud-db-system-connector-connection-status --cloud-db-system-connector-id $cloud_db_system_connector_id

oci_cli/help_text_producer/data_files/text/cmdref/database-management/cloud-db-system-connector/create-cloud-db-system-connector-create-cloud-db-system-macs-connector-details.txt

@@ -0,0 +1,170 @@
+"create-cloud-db-system-connector-create-cloud-db-system-macs-connector-details"
+********************************************************************************
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Creates a new cloud connector.
+
+
+Usage
+=====
+
+   oci database-management cloud-db-system-connector create-cloud-db-system-connector-create-cloud-db-system-macs-connector-details [OPTIONS]
+
+
+Required Parameters
+===================
+
+--agent-id [text]
+
+The OCID of the management agent used for the cloud DB system
+connector.
+
+--cloud-db-system-id [text]
+
+The OCID of the cloud DB system.
+
+
+Optional Parameters
+===================
+
+--connection-info [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. For more information, see Resource Tags. Example:
+*{“Operations”: {“CostCenter”: “42”}}* 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.
+
+--display-name [text]
+
+The user-friendly name for the cloud connector. The name does not have
+to be unique.
+
+--freeform-tags [complex type]
+
+Free-form tags for this resource. Each tag is a simple key-value pair
+with no predefined name, type, or namespace. For more information, see
+Resource Tags. Example: *{“Department”: “Finance”}* 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 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, INACTIVE, NOT_CONNECTED, 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-compartment-id
+       export db_system_discovery_id=<substitute-value-of-db_system_discovery_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-db-system-discovery-id
+       export agent_id=<substitute-value-of-agent_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system-connector/create-cloud-db-system-connector-create-cloud-db-system-macs-connector-details.html#cmdoption-agent-id
+
+       cloud_db_system_id=$(oci database-management cloud-db-system create --compartment-id $compartment_id --db-system-discovery-id $db_system_discovery_id --query data.id --raw-output)
+
+       oci database-management cloud-db-system-connector create-cloud-db-system-connector-create-cloud-db-system-macs-connector-details --agent-id $agent_id --cloud-db-system-id $cloud_db_system_id

oci_cli/help_text_producer/data_files/text/cmdref/{marketplace-publisher/attachment/attachment → database-management/cloud-db-system-connector}/create.txt

@@ -17,39 +17,39 @@
 Description
 ===========
 
-Creates a new Attachment.
+Creates a new cloud connector.
 
 
 Usage
 =====
 
-   oci marketplace-publisher attachment attachment create [OPTIONS]
+   oci database-management cloud-db-system-connector create [OPTIONS]
 
 
 Required Parameters
 ===================
 
---display-name [text]
-
-The name used to refer to the uploaded data.
+--cloud-db-system-id [text]
 
---file-base64-encoded [text]
+The OCID of the cloud DB system.
 
-Base64-encoded file to attach to the Offer. File must be a PDF with
-maximum size of 1 MB
+--connector-type [text]
 
---offer-id [text]
+The type of connector.
 
-unique Offer identifier
-
---type [text]
+Accepted values are:
 
-The type of offer attachment.
+   MACS
 
 
 Optional Parameters
 ===================
 
+--display-name [text]
+
+The user-friendly name for the cloud connector. The name does not have
+to be unique.
+
 --from-json [text]
 
 Provide input to this command as a JSON document from a file using the
@@ -90,7 +90,7 @@ is returned.
 
 Accepted values are:
 
-   ACTIVE, CREATING, DELETED, DELETING, FAILED, UPDATING
+   ACTIVE, CREATING, DELETED, DELETING, FAILED, INACTIVE, NOT_CONNECTED, UPDATING
 
 --wait-interval-seconds [integer]
 
@@ -125,11 +125,10 @@ 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 display_name=<substitute-value-of-display_name> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/offer/offer/create.html#cmdoption-display-name
-       export seller_compartment_id=<substitute-value-of-seller_compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/offer/offer/create.html#cmdoption-seller-compartment-id
-       export file_base64_encoded=<substitute-value-of-file_base64_encoded> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/attachment/attachment/create.html#cmdoption-file-base64-encoded
-       export type=<substitute-value-of-type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/marketplace-publisher/attachment/attachment/create.html#cmdoption-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/database-management/cloud-db-system/create.html#cmdoption-compartment-id
+       export db_system_discovery_id=<substitute-value-of-db_system_discovery_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-db-system-discovery-id
+       export connector_type=<substitute-value-of-connector_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system-connector/create.html#cmdoption-connector-type
 
-       offer_id=$(oci marketplace-publisher offer offer create --display-name $display_name --seller-compartment-id $seller_compartment_id --query data.id --raw-output)
+       cloud_db_system_id=$(oci database-management cloud-db-system create --compartment-id $compartment_id --db-system-discovery-id $db_system_discovery_id --query data.id --raw-output)
 
-       oci marketplace-publisher attachment attachment create --display-name $display_name --file-base64-encoded $file_base64_encoded --offer-id $offer_id --type $type
+       oci database-management cloud-db-system-connector create --cloud-db-system-id $cloud_db_system_id --connector-type $connector_type

oci_cli/help_text_producer/data_files/text/cmdref/database-management/cloud-db-system-connector/delete.txt

@@ -0,0 +1,135 @@
+"delete"
+********
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Deletes the cloud connector specified by *cloudDbSystemConnectorId*.
+
+
+Usage
+=====
+
+   oci database-management cloud-db-system-connector delete [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cloud-db-system-connector-id [text]
+
+The OCID of the cloud connector.
+
+
+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.
+
+--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, INACTIVE, NOT_CONNECTED, 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 compartment_id=<substitute-value-of-compartment_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-compartment-id
+       export db_system_discovery_id=<substitute-value-of-db_system_discovery_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-db-system-discovery-id
+       export connector_type=<substitute-value-of-connector_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system-connector/create.html#cmdoption-connector-type
+
+       cloud_db_system_id=$(oci database-management cloud-db-system create --compartment-id $compartment_id --db-system-discovery-id $db_system_discovery_id --query data.id --raw-output)
+
+       cloud_db_system_connector_id=$(oci database-management cloud-db-system-connector create --cloud-db-system-id $cloud_db_system_id --connector-type $connector_type --query data.id --raw-output)
+
+       oci database-management cloud-db-system-connector delete --cloud-db-system-connector-id $cloud_db_system_connector_id

oci_cli/help_text_producer/data_files/text/cmdref/database-management/cloud-db-system-connector/get.txt

@@ -0,0 +1,98 @@
+"get"
+*****
+
+* Description
+
+* Usage
+
+* Required Parameters
+
+* Optional Parameters
+
+* Global Parameters
+
+* Example using required parameter
+
+
+Description
+===========
+
+Gets the details for the cloud connector specified by
+*cloudDbSystemConnectorId*.
+
+
+Usage
+=====
+
+   oci database-management cloud-db-system-connector get [OPTIONS]
+
+
+Required Parameters
+===================
+
+--cloud-db-system-connector-id [text]
+
+The OCID of the cloud connector.
+
+
+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/database-management/cloud-db-system/create.html#cmdoption-compartment-id
+       export db_system_discovery_id=<substitute-value-of-db_system_discovery_id> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system/create.html#cmdoption-db-system-discovery-id
+       export connector_type=<substitute-value-of-connector_type> # https://docs.cloud.oracle.com/en-us/iaas/tools/oci-cli/latest/oci_cli_docs/cmdref/database-management/cloud-db-system-connector/create.html#cmdoption-connector-type
+
+       cloud_db_system_id=$(oci database-management cloud-db-system create --compartment-id $compartment_id --db-system-discovery-id $db_system_discovery_id --query data.id --raw-output)
+
+       cloud_db_system_connector_id=$(oci database-management cloud-db-system-connector create --cloud-db-system-id $cloud_db_system_id --connector-type $connector_type --query data.id --raw-output)
+
+       oci database-management cloud-db-system-connector get --cloud-db-system-connector-id $cloud_db_system_connector_id