vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud resource service-instance-update ( NAME | ID ) [-n, --name NEW_NAME] [--service-plan-id SERVICE_PLAN_ID] [-p, --parameters @JSON_FILE | JSON_STRING ] [-g RESOURCE_GROUP] [--service-endpoints SERVICE_ENDPOINTS_TYPE] [-f, --force]



 Command options 

Name (required)
: Name of the service instance, exclusive with ID

ID (required)
: ID of the service instance, exclusive with NAME

-n, --name NEW_NAME
: New service instance name

--service-plan-id SERVICE_PLAN_ID
: New Service Plan ID

-p, --parameters @JSON_FILE | JSON_STRING
: JSON file or JSON string of parameters to create service instance

-g RESOURCE_GROUP
: Resource group name

--service-endpoints SERVICE_ENDPOINTS_TYPE
: Types of the service endpoints. Possible values are 'public', 'private', 'public-and-private'.

-f, --force
: Force update without confirmation





 Examples 

Update service instance my-service-instance, change its name to new-service-instance:

ibmcloud resource service-instance-update my-service-instance -n new-service-instance







 ibmcloud resource service-instance-delete 

Delete service instance. If provisioning is in progress, the command attempts to cancel the provisioning process. Some services might not support cancellation.

ibmcloud resource service-instance-delete (NAME|ID) [-f, --force] [--recursive]



 Command options 

Name (required)
: Name of the service instance, exclusive with ID

ID (required)
: ID of the service instance, exclusive with NAME

-f, --force
: Force deletion without confirmation

--recursive
: Delete all belonging resources





 Examples 

Delete resource service-instance my-service-instance:

ibmcloud resource service-instance-delete my-service-instance
c36e9f3a-feaf-4033-8603-687784dc7e51 my-root-key





 Example 2 

List keys and show the cloud resource name (CRN) using the --crn parameter.

 list keys and show the cloud resource name (CRN)
$ ibmcloud kp keys -c

Retrieving keys...
OK
Key ID Key Name CRN
5f2cc155-fe16-492c-845c-4d1f0688c7ba my-root-key crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:5f2cc155-fe16-492c-845c-4d1f0688c7ba
c36e9f3a-feaf-4033-8603-687784dc7e51 my-root-key crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:c36e9f3a-feaf-4033-8603-687784dc7e51





 Example 3 

List keys in JSON format.

The --output json parameter implies the --crn (cloud resource name) parameter.

 list keys
$ ibmcloud kp keys --output json

[
{
"id": "5f2cc155-fe16-492c-845c-4d1f0688c7ba",
"name": "my-root-key",
console.log('listResourceKeys() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

Example response:

{
"rows_count": 1,
"next_url": null,
"resources": [
{
"id": "crn:v1:bluemix:public:cloud-object-storage:global:a/4329073d16d2f3663f74bfa955259139:8d7af921-b136-4078-9666-081bd8470d94:resource-key:23693f48-aaa2-4079-b0c7-334846eff8d0",
"guid": "23693f48-aaa2-4079-b0c7-334846eff8d0",
"url": "/v2/resource_keys/23693f48-aaa2-4079-b0c7-334846eff8d0",
"created_at": "2018-07-02T22:03:43.837979455Z",
"updated_at": "2018-07-02T22:03:43.837979455Z",
"deleted_at": null,
"created_by": "IBMid-5500093BHN",
"updated_by": "IBMid-5500093BHN",
"deleted_by": "",
"source_crn": "crn:v1:bluemix:public:cloud-object-storage:global:a/4329073d16d2f3663f74bfa955259139:8d7af921-b136-4078-9666-081bd8470d94::",
See this topic in the Fabric documentation for more information about [Certificate Revocation Lists](https://hyperledger-fabric-ca.readthedocs.io/en/release-1.4/users-guide.html?highlight=revocation%20listrevoking-a-certificate-or-identity).



This is an example MSP JSON file:

{
"name": "org1msp",
"display_name": "org1msp",
"msp_id": "org1msp",
"type": "msp",
"admins": [
"LS0tLS1CRUd...LS0tLQo="
],
"root_certs": [
"LS0tLS1CRUd...LS0tLS0K"
],
"intermediate_certs": [],
"tls_root_certs": [
"LS0tLS1CRUd...LS0y=g"
],
"tls_intermediate_certs": [],
"fabric_node_ous": {
"admin_ou_identifier": {
"certificate": "LS0tLS1CRUd...LS0tLS0K",
"organizational_unit_identifier": "admin"
},
"client_ou_identifier": {
"certificate": "LS0tLS1CRUd...LS0tLS0K",
"organizational_unit_identifier": "client"
},
"enable": true,
"orderer_ou_identifier": {
"certificate": "LS0tLS1CRUd...LS0tLS0K",
"organizational_unit_identifier": "orderer"
},
"peer_ou_identifier": {
print('nget_resource_key() response:n',
json.dumps(resource_key, indent=2))

getResourceKeyOptions := resourceControllerService.NewGetResourceKeyOptions(
instanceKeyGUID,
)

resourceKey, response, err := resourceControllerService.GetResourceKey(getResourceKeyOptions)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(resourceKey, "", " ")
fmt.Printf("nGetResourceKey() response:n%sn", string(b))

const params = {
id: instanceKeyGuid,
};

resourceControllerService.getResourceKey(params)
.then(res => {
console.log('getResourceKey() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});
3. Copy the service credentials and add them to your application.
4. After the update to the app, deploy the new version to your classic infrastructure assets.
rule_context_model = {
'attributes': [rule_context_attribute_model],
}

resource_attribute_model = {
'name': 'accountId',
'value': '12ab34cd56ef78ab90cd12ef34ab56cd',
}

resource_model = {
'attributes': [resource_attribute_model],
}

out_rule = context_based_restrictions_service.replace_rule(
rule_id='testString',
if_match='testString',
contexts=[rule_context_model],
resources=[resource_model],
description='this is an example of rule',
enforcement_mode='disabled'
).get_result()

print(json.dumps(out_rule, indent=2))

ruleContextAttributeModel := &contextbasedrestrictionsv1.RuleContextAttribute{
Name: core.StringPtr("networkZoneId"),
Value: core.StringPtr("76921bd873115033bd2a0909fe081b45"),
}

ruleContextModel := &contextbasedrestrictionsv1.RuleContext{
Attributes: []contextbasedrestrictionsv1.RuleContextAttribute{ruleContextAttributeModel},
}

resourceAttributeModel := &contextbasedrestrictionsv1.ResourceAttribute{
Name: core.StringPtr("accountId"),
Value: core.StringPtr("12ab34cd56ef78ab90cd12ef34ab56cd"),
}

resourceModel := &contextbasedrestrictionsv1.Resource{
Attributes: []contextbasedrestrictionsv1.ResourceAttribute{resourceAttributeModel},
}
You cannot restore a key that has an expiration date that is current or in the past.

$ curl -X POST "https://<region>.kms.cloud.ibm.com/api/v2/keys/<keyID_or_alias>/restore" -H "authorization: Bearer <IAM_token>" -H "bluemix-instance: <instance_ID>" -H "x-kms-key-ring: <key_ring_ID>"

Replace the variables in the example request according to Table 2.





Table 2. Describes the variables that are needed to restore keys with the Key Protect API

 Variable Description 

 region Required. The region abbreviation, such as us-south or eu-gb, that represents the geographic area where your Key Protect instance resides. For more information, check out [Regional service endpoints](https://cloud.ibm.com/docs/key-protect?topic=key-protect-regionsservice-endpoints). 
 keyID_or_alias Required. The unique identifier or alias for the key that you want to restore. 
 IAM_token Required. Your IBM Cloud access token. Include the full contents of the IAM token, including the Bearer value, in the curl request. For more information, check out [Retrieving an access token](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-access-token). 
 instance_ID Required. The unique identifier that is assigned to your Key Protect service instance. For more information, check out [Retrieving an instance ID](https://cloud.ibm.com/docs/key-protect?topic=key-protect-retrieve-instance-ID). 
 key_ring_ID Optional. The unique identifier of the key ring that the key is a part of. If unspecified, Key Protect will search for the key in every key ring associated with the specified instance. It is therefore recommended to specify the key ring ID for a more optimized request.
Delete a Satellite Connector.

ibmcloud sat experimental connector rm --connector-id ID [-q]



 Command options 

--connector-id ID
: Required. Enter the ID of the Connector to delete.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat experimental connector rm --connector-id myconnector









 Resource commands 

Use these commands to view the Kubernetes resources that run in clusters that are registered with [Satellite Configuration](https://cloud.ibm.com/docs/satellite?topic=satellite-setup-clusters-satconfig).



 ibmcloud sat resource get 

Get the details of a Kubernetes resource that is managed by a Satellite configuration.

ibmcloud sat resource get --resource RESOURCE [--save-data] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--resource RESOURCE
: Required. The ID of the Kubernetes resource. To list Kubernetes resources, run ibmcloud sat resource ls.

--save-data
: Optional. Download and save the Kubernetes resource definition to a temporary file.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat resource get --resource 1234567







 ibmcloud sat resource history get 

Get the history of a Kubernetes resource.

ibmcloud sat resource history --resource RESOURCE [--limit LIMIT] [--output json] [-q]



 Minimum required permissions 

IBM Cloud IAM Viewer platform role for the Resource resource in Satellite.
Date: Mon, 04 Mar 2019 05:29:49 GMT
Content-Type: application/json
Content-Length: 4653
Connection: keep-alive
X-Powered-By: Servlet/3.1
Cache-Control: no-cache, no-store, must-revalidate
Content-Language: en-US
ibm-mq-rest-gateway-qmgr: QM1
Strict-Transport-Security: max-age=31536000; includeSubDomains

Note : Any of the queue managers used above i.e. gateway queue manager or remote queue manager can be replaced with any other IBM MQ queue managers and used.

--------------------





 Appendix 



 Appendix 1: connection_info.txt 

To retrieve the connection_info.txt file containing queue manager connection details:



1. Log in to the IBM cloud service instance by clicking on the relevant service shown in the table (./images/mqoc_remote_administration_two_qmgr_console.png)Image showing service instance][!!]
2. This will open the queue manager view. Select the queue manager you wish to retrieve the connection info from ![Image showing list of queue managers](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_qmview.png)
3. Click Connection information![Image of queue manager connection information](https://cloud.ibm.com/docs-content/v1/content/3a120b16db5fdc3e70d071af8a63ce5515c1b096/mqcloud/images/mqoc_connection_info.png)
4. Download this file in 'JSON text format'







 Appendix 2: platformApiKey.json 

To create or reset your administrator api key:



1.
"name": "us-east"
},
{
"href": "https://us-east.iaas.cloud.ibm.com/v1/regions/us-east/zones/us-east-2"
}
],
},
"resource_type": "backup_policy_plan"
}





 Deleting a backup policy and plans with the API 

Make a DELETE /backup_policies/{backup_policy_id} request to delete a backup policy and all associated backup plans. During the deletion, the status shows deleting. When the deletion is complete (status = deleted), the backup policy and backup plans cannot be recovered.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/backup_policies/5063bfe5-c16f-4606-ba26-fba0f099b97d?version=2022-06-28&generation=2" -H "Authorization: $iam_token"

The response indicates that all backup plans are deleted.





 Deleting a backup plan with the API 

Make a DELETE /backup_policies/{backup_policy_id}/plans/{plan_id} request to delete a specific backup plan from a backup policy. Resources that were created by the plan remain but they are no longer subject to the plan's deletion trigger. During the deletion, the status shows deleting. When the deletion is complete (status = deleted), the backup plan cannot be recovered.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/backup_policies/5063bfe5-c16f-4606-ba26-fba0f099b97d/plans/4cf9171a-0043-4434-8727-15b53dbc374c?version=2022-06-28&generation=2" -H "Authorization: $iam_token"

The response shows that the backup plan was deleted.

{
}
]





 Example 4 

List keys and iterate over them, showing details.

 list keys and convert to a list
$ KEYS=$(ibmcloud kp keys --output json | jq -r '.[] | .id')

$ for key in $(echo "${KEYS}"); do
ibmcloud kp key show ${key}
done

Grabbing info for key id: 5f2cc155-fe16-492c-845c-4d1f0688c7ba...
OK
Key ID Key Name Description Creation Date Expiration Date
5f2cc155-fe16-492c-845c-4d1f0688c7ba my-root-key 2020-05-10 18:04:01 +0000 UTC Key does not expire

Grabbing info for key id: c36e9f3a-feaf-4033-8603-687784dc7e51...
OK
Key ID Key Name Description Creation Date Expiration Date
c36e9f3a-feaf-4033-8603-687784dc7e51 my-root-key 2020-05-10 17:56:37 +0000 UTC Key does not expire





 Example 5 

Create 20 keys and show them in groups of 5 using the kp keys -n -s options.

 create 20 test keys
$ for I in {1..20}; do
KEY_ID=$(ibmcloud kp key create my-test-key-$I --output json | jq -r '.["id"]')
KEY_NAME=$(ibmcloud kp key show $KEY_ID --output json | jq -r '.["name"]')
echo $KEY_ID $KEY_NAME
done

b70f62a1-4d52-4526-91a9-ce47bf14c2a5 my-test-key-1
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:390086ac-76fa-4094-8cf3-c0829bd69526:key:c36e9f3a-feaf-4033-8603-687784dc7e51"
}
]





 Example 4 

List keys and iterate over them, showing details.

 list keys and convert to a list
$ KEYS=$(ibmcloud kp keys --output json | jq -r '.[] | .id')

$ for key in $(echo "${KEYS}"); do
ibmcloud kp key show ${key}
done

Grabbing info for key id: 5f2cc155-fe16-492c-845c-4d1f0688c7ba...
OK
Key ID Key Name Description Creation Date Expiration Date
5f2cc155-fe16-492c-845c-4d1f0688c7ba my-root-key 2020-05-10 18:04:01 +0000 UTC Key does not expire

Grabbing info for key id: c36e9f3a-feaf-4033-8603-687784dc7e51...
OK
Key ID Key Name Description Creation Date Expiration Date
c36e9f3a-feaf-4033-8603-687784dc7e51 my-root-key 2020-05-10 17:56:37 +0000 UTC Key does not expire





 Example 5 

Create 20 keys and show them in groups of 5 using the kp keys -n -s options.

 create 20 test keys
$ for I in {1..20}; do
KEY_ID=$(ibmcloud kp key create my-test-key-$I --output json | jq -r '.
"region": [
{
"name": "us-east"
},
{
"href": "https://us-east.iaas.cloud.ibm.com/v1/regions/us-east/zones/us-east-2"
}
],
},
"resource_type": "backup_policy_plan"
}
Show more





 Deleting a backup policy and plans with the API 

Make a DELETE /backup_policies/{backup_policy_id} request to delete a backup policy and all associated backup plans. During the deletion, the status shows deleting. When the deletion is complete (status = deleted), the backup policy and backup plans cannot be recovered.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/backup_policies/5063bfe5-c16f-4606-ba26-fba0f099b97d?version=2022-06-28&generation=2" -H "Authorization: $iam_token"

The response indicates that all backup plans are deleted.





 Deleting a backup plan with the API 

Make a DELETE /backup_policies/{backup_policy_id}/plans/{plan_id} request to delete a specific backup plan from a backup policy. Resources that were created by the plan remain but they are no longer subject to the plan's deletion trigger. During the deletion, the status shows deleting. When the deletion is complete (status = deleted), the backup plan cannot be recovered.

See the following example.

curl -X DELETE "$vpc_api_endpoint/v1/backup_policies/5063bfe5-c16f-4606-ba26-fba0f099b97d/plans/4cf9171a-0043-4434-8727-15b53dbc374c?version=2022-06-28&generation=2" -H "Authorization: $iam_token"
To view your service resource key, enter the following command:

ibmcloud resource service-key <service_key_name>

Required parameter:



* <service key name>: the name of the service key that you entered when creating the key.



Sample Response: Bear in mind that the cluster credentials are not returned in the response.

{
"apikey": "xxxxx",
"endpoints": {
"applications_api": "https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/xxxx-3bxxxbc-4xxx1-axx6-8xxdxx0xxd/spark_applications",
"instance_api": "https://api.us-south.ae.cloud.ibm.com/v3/analytics_engines/xxxx-3bxxxbc-4xxx1-axx6-8xxdxx0xxd",
"history_server_ui": "https://spark-console.us-south.ae.cloud.ibm.com/v3/analytics_engines/xxxx-3bxxxbc-4xxx1-axx6-8xxdxx0xxd/spark_history_ui",
"history_server_api":"https://spark-console.us-south.ae.cloud.ibm.com/v3/analytics_engines/xxxx-3bxxxbc-4xxx1-axx6-8xxdxx0xxd/spark_history_api/v1"
},
"iam_apikey_description": "Auto-generated for key cabde209-xxxx",
"iam_apikey_name": "Service credentials-1",
"iam_role_crn": "crn:v1:bluemix:public:iam::::serviceRole:Reader",
[Menu icon](https://cloud.ibm.com/docs-content/v1/content/af86f2de476b09efc2fa731457e7b3e58571f062/icons/icon_hamburger.svg) from the upper left, then click Classic Infrastructure.
3. Choose Network > Gateway Appliances.
4. Click the gateway appliance name to access the gateway appliance details page. You can find the license expiration date in the Details section.



To view your current license expiration from the vSRX CLI, run show system license. You should see the 2024 expiration date for each of the license features on each node.





 Renewing your license 

To renew your license, first run a [Readiness check](https://cloud.ibm.com/docs/vsrx?topic=vsrx-vsrx-readiness) for “License update/renew”. After you address any errors that are found, follow these steps:



1. Open the [IBM Cloud console](https://cloud.ibm.com/vpc-ext) and log in to your account.
2. Select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/af86f2de476b09efc2fa731457e7b3e58571f062/icons/icon_hamburger.svg) from the upper left, then click Classic Infrastructure.
3. Choose Network > Gateway Appliances.
4. Click the gateway appliance name to access the gateway appliance details page.
5. Click Renew license.



The license renewal can take up to 30 minutes to complete. To verify that the process completed successfully, follow the preceding steps in [Viewing your license expiration date](https://cloud.ibm.com/docs/vsrx?topic=vsrx-license-renewallicense-view-steps). Verify that the expiration shows a 2024 expiration.
To retrieve a list of your available keys, run the [kp keys](https://cloud.ibm.com/docs/cli?topic=cli-key-protect-cli-referencekp-keys) command.







 Optional parameters 



* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.









 kp key show 

Retrieve details about a key, such as the key metadata and key material.

If the key was designated as a root key, the system cannot return the key material for that key.

ibmcloud kp key show KEY_ID_OR_ALIAS
-i, --instance-id INSTANCE_ID
[--key-ring KEY_RING_ID]
[-o, --output OUTPUT]



 Examples 

These are examples of kp key show.



 Example 1 

Create a root key and show the details.

 create a root key
$ ibmcloud kp key create my-root-key

Creating key: 'my-root-key', in instance: '390086ac-76fa-4094-8cf3-c0829bd69526'...
OK
Key ID Key Name
8635b804-9966-4918-a16b-d561fdbf181f my-root-key

 show key details
$ ibmcloud kp key show 8635b804-9966-4918-a16b-d561fdbf181f

Grabbing info for key id: 8635b804-9966-4918-a16b-d561fdbf181f...
OK
Key ID Key Name Description Creation Date Expiration Date
8635b804-9966-4918-a16b-d561fdbf181f my-root-key 2020-05-05 19:58:02 +0000 UTC Key does not expire





 Example 2 

This is an explanation of the JSON keys and values from the kp key show command.
"node": "4.2.4",
"npm": "3.10.10"
}
}





 App restarts due to memory constraints 

Node.js does not know how much memory is available to the app, so the garbage collector might not run before memory is exhausted.

2017-09-01T11:00:42.19-0400 [APP/PROC/WEB/0]OUT Exit status 137
2017-09-01T11:00:42.23-0400 [CELL/0] OUT Exit status 0
2017-09-01T11:00:42.27-0400 [CELL/0] OUT Destroying container
2017-09-01T11:00:42.34-0400 [API/0] OUT Process has crashed with type: "web"
2017-09-01T11:00:42.36-0400 [API/0] OUT App instance exited with guid eecfba3b-430c-4a6b-b71f-ac72816fe152 payload: {"instance"=>"77dbb981-16d0-3a05-3235-9a4b", "index"=>0, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:nn* 2 error(s) occurred:nn Exited with status 137 (out of memory)n cancelledn cancelled", "crash_count"=>1, "crash_timestamp"=>1504278042244633291, "version"=>"6497b5b5-67d4-4c5a-b1af-362e522a029d"}
2017-09-01T11:00:43.35-0400 [CELL/0] OUT Successfully destroyed container

A possible solution is to set the --max_old_space_size option on the app's start command in the package.json file. This option represents part of the app's memory footprint and should be set to a value less than the total memory available to the app.
fmt.Printf("nCreateResourceKey() response:n%sn", string(b))

const parameters = {
'exampleParameter': 'exampleValue'
};

const params = {
name: keyName,
source: instanceGuid,
parameters: parameters,
};

resourceControllerService.createResourceKey(params)
.then(res => {
instanceKeyGuid = res.result.guid;
console.log('createResourceKey() response:n' + JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});



* To retrieve service credentials, call the [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controllerget-resource-key) as shown in the following example request and pass the ID associated with the instance.





* Curl
* Java
* Python
* Go
* Node



curl -X GET https://resource-controller.cloud.ibm.com/v2/resource_keys/23693f48-aaa2-4079-b0c7-334846eff8d0 -H 'Authorization: Bearer <IAM_TOKEN>'

GetResourceKeyOptions getResourceKeyOptions = new GetResourceKeyOptions.Builder()
.id(instanceKeyGuid)
.build();

Response<ResourceKey> response = service.getResourceKey(getResourceKeyOptions).execute();
ResourceKey resourceKey = response.getResult();

System.out.printf("getResourceKey() response:n%sn", resourceKey.toString());

resource_key = resource_controller_service.get_resource_key(
id=instance_key_guid
).get_result()
Code and processes using this field must tolerate unexpected values. <br>Possible values: [pending,approved,rejected,expired,detached] 
 status <br>string Connection's current configuration state. The list of enumerated values for this property may expand in the future. Code and processes using this field must tolerate unexpected values. <br>Possible values: [attached,failed,pending,deleting,detaching,detached] 
 updated_at <br>date-time The date and time that this connection was last updated 
 zone <br>ZoneReference The location of the GRE tunnel. This field only applies to gre_tunnel and unbound_gre_tunnel type connections. 
 <br><br> * name <br> Always included <br> string<br><br><br> Availability zone name <br>Example:us-south-1 





Table 4. Status codes

 Status Code 

 200 The connection was updated successfully. 
 400 The connection update template was invalid. 
 404 A connection or gateway with the specified identifier(s) could not be found. 





 Example Response 

The following response indicates that the connection was updated successfully:

{
"name": "Transit_Service_BWTN_SJ_DL",
"network_id": "crn:v1:bluemix:public:is:us-south:a/123456::vpc:4727d842-f94f-4a2d-824a-9bc9b02c523b",
"network_type": "vpc",
"id": "1a15dca5-7e33-45e1-b7c5-bc690e569531",
"base_connection_id": "975f58c1-afe7-469a-9727-7f3d720f2d32",
"created_at": "2022-02-10T14:52:54.918Z",
"local_bgp_asn": 64490,