vania-janet/multiturn-rag-retrieval-data huggingface dataset:
--all-resource-groups
: Query all resource groups

--long
: Show more fields in output.





 Examples 

List service instances of service test-service:

ibmcloud resource service-instances --service-name test-service







 ibmcloud resource service-instance 

Show details of a service instance.

ibmcloud resource service-instance (NAME|ID) [--location LOCATION] [--id]



 Command options 

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

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

--location
: Filter by location

--id
: Display the ID of service instance





 Examples 

Show details of service instance my-service-instance:

ibmcloud resource service-instance my-service-instance







 ibmcloud resource service-instance-create 

Create a service instance.

ibmcloud resource service-instance-create NAME (SERVICE_NAME | SERVICE_ID) SERVICE_PLAN_NAME LOCATION [-d, --deployment DEPLOYMENT_NAME] [-p, --parameters @JSON_FILE | JSON_STRING ] [-g RESOURCE_GROUP] [--service-endpoints SERVICE_ENDPOINTS_TYPE] [--allow-cleanup] [--lock]



 Command options 

NAME (required)
: Name of the service instance

SERVICE_NAME or SERVICE_ID (required)
: Name or ID of the service. To list service offerings, use the ibmcloud catalog service-marketplace[command](https://cloud.ibm.com/docs/cli/reference/ibmcloud?topic=cli-ibmcloud_catalogibmcloud_catalog_service_marketplace).

SERVICE_PLAN_NAME or SERVICE_PLAN_ID (required)
: Name or ID of the service plan

LOCATION (required)
: Target location or environment to create the service instance

-d, --deployment DEPLOYMENT_NAME
: Name of the deployment

-p, --parameters @JSONFILE or JSON_STRING
: JSON file or JSON string of parameters to create service instance
,0.004235421773046255,0.0011601535370573401],0.004270229954272509,0.0011619371362030506],0.004301954992115498,0.00116356264334172],0.004330573603510857,0.0011650290107354522],0.004356065299361944,0.0011663351906463504],0.004378411453217268,0.0011674802517518401],0.004397595766931772,0.001168463146314025],0.004413604270666838,0.0011692834086716175],0.004426425322890282,0.001169940340332687],0.004436049144715071,0.0011704334756359458],0.004442468751221895,0.0011707624653354287],0.004446081351488829,0.0011709475656971335],0.004446081351488829,0.0011709475656971335],0.004446081351488829,0.0011709475656971335],0.004446081351488829,0.0011709475656971335
Supports regular expression if the condition is set to matches_regex. 



Notes:



* If the rule type is header, the following characters are not allowed for field and value: "(),/:;<=>?@[ ! ! ! ! ]{}'. * If the rule type is body, the following characters are not allowed for field and value: "'=,()& and space. * If the rule type is query, field and value must be a percent-encoded string.<-- </ul> --><-- </section "id="section-layer-7-rule-properties" "> --><-- <section "id="section-layer-7-examples-create-policy-and-rules" "> --> Examples: Creating policies and rules The following layer 7 examples show how policies and rules are created and associated with a listener.<-- <section "id="section-create-https-listener-redirect" "> --> Example 1: Create an HTTPS listener with redirect policies curl -H "Authorization: $iam_token" -X POST
"$vpc_api_endpoint/v1/load_balancers/$lbId/listeners" -d '{
"certificate_instance": {
"crn": "crn:v1:staging:public:cloudcerts:us-south:a/1111111111111111111111111111:22222222-3333-4444-5555-666666666666:certificate:77777777777777777777777777777777"
},
"connection_limit": 2000,
"port": 443,
"protocol": "https",
"policies":
{
"name": "hostname_header",
"action": "redirect",
"priority": 1,
"target": {
"url": "https://www.examples.com/",
{"firefox": { <br>"name": "Firefox", <br>"pref_url": "about:config" <br>}} STRING JSON Dictionary or List of Dictionary {'firefox': {'name': 'Firefox', 'pref_url': 'about:config'}} 
 men: <br>- John Smith <br>- Bill Jones <br>women: <br>- Mary Smith <br>- Susan Williams STRING YAML Dictionary {'men': ['John Smith', 'Bill Jones'], 'women': ['Mary Smith', 'Susan Williams']} 





 Feature flag 

feature = appconfig_client.get_feature('json-feature')
feature.get_feature_data_type() // STRING
feature.get_feature_data_format() // JSON
feature.get_current_value(entityId, entityAttributes) // returns single dictionary object or list of dictionary object

// Example Below
// input json :- [{"role": "developer", "description": "do coding"},{"role": "tester", "description": "do testing"}]
// expected output :- "do coding"

tar_val = feature.get_current_value(entityId, entityAttributes)
expected_output = tar_val[0]

// input json :- {"role": "tester", "description": "do testing"}
// expected output :- "tester"

tar_val = feature.get_current_value(entityId, entityAttributes)
expected_output = tar_val['role']

feature = appconfig_client.getFeature('yaml-feature')
feature.get_feature_data_type() // STRING
feature.get_feature_data_format() // YAML
feature.get_current_value(entityId, entityAttributes) // returns dictionary object
:1,0]}],{"q":7,"scale":1,0]}],{"q":12,"scale":1,0]}],{"q":8,"scale":1,0]}],{"q":14,"scale":1,0]}],{"q":10,"scale":1,0]}],{"q":13,"scale":1,0]}],{"q":15,"scale":1,0]}],{"q":12,"scale":1,0]}],{"q":14,"scale":1,0]}],{"q":11,"scale":1,0]}],{"q":13,"scale":1,0]}],{"q":16,"scale":1,0]}],{"q":12,"scale":1,0]}],{"q":18,"scale":1,0]}],{"q":14,"scale":1,0]}],{"q":19,"scale":1,0]}],{"q":18,"scale":1,0]}],{"q":15,"scale":1,0]}],{"q":17,"
-----------+-------------+--------+---------------------+---------------------
1001 Jacket 102.00 2020-10-23 16:00:00 
1002 Gloves 20.50 2020-10-23 16:05:00 
1003 Hat 18.99 2020-10-23 16:10:00 
1004 | Shoes | 125.25 | 2020-10-23 16:15:00 | 2020-10-23 17:00:00
1004 Shoes 100.00 2020-10-23 17:00:00 
(5 rows)

In this example, the query searched for all the changes that happened to the product table during a certain period of time, up to and including the AND timestamp.

See also [the BETWEEN...AND subclause](https://cloud.ibm.com/docs/netezza?topic=netezza-runningqueries_tt).







 Recovering tables 

BEGIN;
ALTER TABLE <table_name> RENAME TO <new_table_name>;
CREATE TABLE <table_ name> AS
SELECT * FROM <new_table_name> FOR SYSTEM_TIME <temporal_clause>;
DROP TABLE <new_table_name>; -- or, keep it for diagnostics
COMMIT;

Example:

BEGIN;
ALTER TABLE PRODUCT RENAME TO PRODUCT_BAK;
CREATE TABLE PRODUCT AS
SELECT * FROM FLIGHT_BAK FOR SYSTEM_TIME AS OF '2022-11-01 11:30:00';
DROP TABLE FLIGHT_BAK; -- or, keep it for diagnostics
COMMIT;

In this example, you suspected that incorrect bulk changes were made to the PRODUCT table, and you wanted to revert them.





 Restoring updated rows 

UPDATE <table> SET <col> = <expression> [, <col> = <expression>...]
FROM (SELECT <col> [, <col> ...]
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/eca6556f-f67d-4a3e-8428-3db8819fc60c",
"id": "eca6556f-f67d-4a3e-8428-3db8819fc60c",
"lifecycle_state": "stable",
"match_resource_types": [

"volume"
]
],
"match_user_tags": [
"my-daily-backup-policy"
],
"name": "my-backup-policy",
"plans": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/eca6556f-f67d-4a3e-8428-3db8819fc60c/plans/f0b3740b-83b6-4426-af99-140b90ad6f33",
"id": "f0b3740b-83b6-4426-af99-140b90ad6f33",
"name": "my-policy-plan",
"resource_type": "backup_policy_plan"
}
],
"resource_group": {
"crn": "crn:v1:bluemix:public:resource-controller::a/123456::resource-group:fee82deba12e4c0fb69c3b09d1f12345",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/fee82deba12e4c0fb69c3b09d1f12345",
"id": "fee82deba12e4c0fb69c3b09d1f12345",
"name": "my-resource-group"
[Shows the edit dialog for the dictionary entry with synonyms that are specified for a term.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-dictionary-synonym.png)

Figure 32. Synonyms are specified for a term
5. Click Save dictionary.

You can choose a field in the document where you want the enrichment to be applied. Let's choose the subtitle field that was generated when we created the user-trained SDU model. From the Fields to enrich field, select subtitle. Click Apply.

Zoom

![Shows the dialog that asks where to apply the dictionary enrichment.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-dictionary-apply.png)

Figure 33. Choosing where to apply the dictionary enrichment

The dictionary is created and each subtitle in the document is analyzed for mentions of terms or synonyms that are defined in the dictionary. Any mentions that are found are noted in the index.
6. Click Improve and customize from the navigation panel.
7. From the Improvement tools panel of the Improve and customize page, expand Customize display, and then click Facets.
8. Click New facet, and then select From existing fields in a collection.

Zoom

![Shows the options for creating a facet.](https://cloud.ibm.com/docs-content/v1/content/f16b1f78a92498247223b337bd9303c2758b9ba8/discovery-data/images/tut-sdu-facet-from-field.png)

Figure 34.
","parameters":{"date":"2022-03-29T16:20:11Z","name":"gate_length","unit":"ns","value":1077.3333333333333}],"qubits":13]},{"gate":"reset","name":"reset14","parameters":{"date":"2022-03-29T16:20:11Z","name":"gate_length","unit":"ns","value":1077.3333333333333}],"qubits":14]},{"gate":"reset","name":"reset15","parameters":{"date":"2022-03-29T16:20:11Z","name":"gate_length","unit":"ns","value":1077.3333333333333}],"qubits":15]},{"gate":"reset","name":"reset16","parameters":{"date":"2022-03-29T16:20:11Z","name
"crn": "crn:...]",
"encryption": "provider_managed",
"health_reasons": ],
"health_state": "ok",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/89ba05e9-6e35-4964-9747-7ae3f9b30303",
"id": "89ba05e9-6e35-4964-9747-7ae3f9b30303",
"iops": 1000,
"name": "volume-3",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/volume/profiles/5iops-tier",
"name": "5iops-tier"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
"id": "4bbce614c13444cd8fc5e7e878ef8e21",
"name": "Default"
},
"status": "available",
"status_reasons": ],
"user_tags": ],
"volume_attachments": ],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2",
"resource_type": "zone"
}
}
]
}





 Viewing volume details with the API 

Make a GET /volumes/{id} call to see details of a volume. See the following example.
a7ba-b6f0435c9673/catalog --header 'Authorization: Bearer TOKEN' --header 'Content-Type: application/json' --data '{
"category": "virtual machine"
}'





 Adding search keywords 

You can programmatically add relevant keywords to your product by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellupdate-catalog) as shown in the following sample request. The example adds the ["vm","vsi","virtual machine"] keywords to the product:

curl --request PATCH --url https://product-
lifecycle.api.cloud.ibm.com/openapi/v1/products/9fab83da-98cb-4f18-
a7ba-b6f0435c9673/catalog --header 'Authorization: Bearer TOKEN' --header 'Content-Type: application/json' --data '{
"keywords": "["vm","vsi","virtual machine"]"
}'







 Defining your product page by using the API 

You can programmatically define your product page by calling the Partner Center Sell API. When users select your product from the catalog, they are directed to additional details, including a list of features and supporting media. These details are displayed on the About tab within your product page.



 Providing a list of product features 

You can programmatically provide a list of features that highlight your product's attributes and benefits for users by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellupdate-catalog) as shown in the following sample request. The example adds a feature to the product that is named Best feature with the This is the main feature of my product. description:

curl --request PATCH --url https://product-
lifecycle.api.cloud.ibm.com/openapi/v1/products/9fab83da-98cb-4f18-
},
]
}

This API lists the detailed information with respect to the blueprint ID.

Example

GET /v2/blueprints/Blueprint-Basic-Test-API.soB.347a/ HTTP/1.1
Host: schematics.cloud.ibm.com
Content-Type: application/json
Authorization: Bearer <auth_token>

Output

{
"name": "Blueprint Basic Test API",
"source": {
"source_type": "git_hub",
"git": {
"git_repo_url": "https://github.com/Cloud-Schematics/blueprint-basic-example",
"git_repo_folder": "basic-blueprint.yaml",
"git_branch": "main",
"git_commit": "68ce0e62f2e1b33c2341fc35fb125ffe998128d6",
"git_commit_timestamp": "2022-11-15 11:08:48 +0000 UTC"
},
"catalog": {},
"cos_bucket": {}
},
"config": [
{
"source": {
"source_type": "git_hub",
"git": {
"git_repo_url": "https://github.com/Cloud-Schematics/blueprint-basic-example",
"git_repo_folder": "basic-input.yaml",
"git_branch": "main",
"git_commit": "68ce0e62f2e1b33c2341fc35fb125ffe998128d6",
"git_commit_timestamp": "2022-11-15 11:08:48 +0000 UTC"
},
"catalog": {},
* Request body -

{
"parameters": [primaryVolumeSnapshotId, true OR false]
}







 SOAP API example 



* URL - https://api.softlayer.com/soap/v3.1/SoftLayer_Network_Storage
* Type - POST
* Request body -

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://api.service.softlayer.com/soap/v3.1/">
<SOAP-ENV:Header>
<ns1:authenticate>
<username>USERNAME</username>
<apiKey>APIKEY</apiKey>
</ns1:authenticate>
<ns2:SoftLayer_Network_StorageInitParameters>
<id>duplicate Volume Id</id>
</ns2:SoftLayer_Network_StorageInitParameters>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:refreshDuplicate>
<snapshotId xsi:type="int">primary Volume Snapshot Id</snapshotId>
<forceRefresh xsi:type="boolean">true</forceRefresh> <-- (remove this tag for normal refresh)
</ns1:refreshDuplicate>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>



For more information about the API and the options, see the [API Reference](https://sldn.softlayer.com/reference/softlayerapi/) and [SoftLayer_Network_Storage::refreshDuplicate](https://sldn.softlayer.com/reference/services/SoftLayer_Network_Storage/refreshDuplicate/).







 Converting a dependent volume to an independent duplicate with the API
<-- </section "class="ph" id="section-target-validate-api-cos" "> --><-- <section "class="ph" id="section-target-view-api-cos" "> --> Viewing a target using the API You can use the following cURL command to view the configuration details of 1 target: curl -X GET <ENDPOINT>/api/v2/targets/<TARGET_ID> -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"
Where<-- <ul> --> * <ENDPOINT> is the API endpoint in the region where you plan to configure or manage a target. For more information, see Endpoints]Endpoints 1] ! ! ! ! . * <TARGET_ID> is the ID of the target.<-- </ul> -->For example, you can run the following cURL request to get information about a target with the ID 00000000-0000-0000-0000-000000000000: curl -X GET https://private.us-south.atracker.cloud.ibm.com/api/v2/targets/00000000-0000-0000-0000-000000000000 -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"
Results will show if the target is COS ("target_type": "cloud_object_storage") or an IBM Cloud Activity Tracker Event Routing hosted event search offering ("target_type": "logdna").<-- </section "class="ph" id="section-target-view-api-cos" "> --><-- <section "class="ph" id="section-target-list-targets-cos" "> --> Listing all targets using the API You can use the following cURL command to view all targets: curl -X GET <ENDPOINT>/api/v2/targets -H "Authorization: $ACCESS_TOKEN" -H "content-type: application/json"
This Postman collection is provided as a starting point for experimenting with the API, and it not intended for production use:

{
"info": {
"_postman_id": "56d99641-9ad6-4218-b3d4-18ac8f3361e0",
"name": "IBM COS",
"description": "IBM COS samples",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json"
},
"item": [
{
"name": "Retrieve list of buckets",
"event":
{
"listen": "test",
"script": {
"id": "d67afcf2-6d35-4a2a-9542-b8d5df78eded",
"type": "text/javascript",
"exec":
"pm.test("Request was successful", function() {",
" pm.response.to.be.success; ",
"});",
"",
"pm.test("Response contains expected content", function() {",
" pm.expect(pm.response.text()).to.include("ListAllMyBucketsResult");",
"});"
]
}
}
],
"request": {
"auth": {
"type": "bearer",
"bearer":
{
"key": "token",
"value": "{{iamtoken}}",
"type": "string"
}
]
},
"method": "GET",
"header":
{
"key": "ibm-service-instance-id",
"value": "{{serviceid}}"
}
],
"id": "fb721535-2cc6-45d6-ade7-3ceb95b7f26f",
"lifecycle_state": "stable",
"match_resource_types": [

"volume"
]
],
"match_user_tags": [
"my-daily-backup-policy"
],
"name": "my-backup-policy",
"plans": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f/plans/4cf9171a-0043-4434-8727-15b53dbc374c",
"id": "4cf9171a-0043-4434-8727-15b53dbc374c",
"name": "my-policy-plan",
"resource_type": "backup_policy_plan"
}
],
"resource_group": {
"crn": "crn:v1:bluemix:public:resource-controller::a/123456::resource-group:20b0c459-3cc6-411b-ba4b-2daa89c8c1b7",
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/20b0c459-3cc6-411b-ba4b-2daa89c8c1b7",
"id": "20b0c459-3cc6-411b-ba4b-2daa89c8c1b7",
"name": "my-resource-group"
},
"resource_type": "backup_policy"
}





 Listing all plans for a backup policy with the API
"id": "5821d0c4-a089-4957-b5fa-03b7ac636c15",
"name": "my-vpc",
"resource_type": "vpc"
}
}





 View a source file share for a replica file share with the API 

Make a GET /shares/{replica_id}/source request and specify the replica share ID to retrieve the source file share details.

curl -X GET "$vpc_api_endpoint/v1/shares/$replica_id/source?version=2023-07-05&generation=2&maturity=beta" -H "Authorization: $iam_token"

A successful response provides details of the source file share. Notice that the replication role is source.

{
"access_control_mode": "security_group",
"created_at": "2023-07-05T22:58:49.000Z",
"crn": "crn:[...]",
"encryption": "provider_managed",
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/207721a9-aff9-4b16-9823-fe68096aeac3",
"id": "207721a9-aff9-4b16-9823-fe68096aeac3",
"iops": 14400,
"lifecycle_state": "stable",
"mount_targets": [
{
"href": "https://us-south.iaas.cloud.ibm.com/v1/shares/207721a9-aff9-4b16-9823-fe68096aeac3/mount_targets/ce244454-0919-45e2-b14b-f4285afcd856",
"id": "ce244454-0919-45e2-b14b-f4285afcd856",
Contributing 

The IBM Cloud API Handbook is open source and corrections and contributions may be made by clicking the Open Issue or Edit Topic links at the top of each page.
"id": "678523bcbe2b4eada913d32640909956",
"name": "Default"
},
"resource_type": "snapshot",
"service_tags": ],
"size": 1,
"source_image": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/images/23045dc2-b463-4cda-b424-bc3dcf51dfbb",
"id": "23045dc2-b463-4cda-b424-bc3dcf51dfbb",
"name": "ubuntu-20-04-minimal-amd64-1"
},
"source_volume": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/8948ad59-bc0f-7510-812f-5dc64f59fab8",
"id": "8948ad59-bc0f-7510-812f-5dc64f59fab8",
"name": "instance-vol1"
},
"user_tags": ]
}
],
"total_count": 2
}





 Listing details of a snapshot with the API 

For details about a single snapshot, use the VPC API to make a GET /snapshots call and specify the snapshot ID.

curl -X GET "$vpc_api_endpoint/v1/snapshots/7528eb61-bc01-4763-a67a-a414a103f96d?version=2022-12-16&generation=2" -H "Authorization: $iam_token"

A successful response looks like the following example.

{
ibmcloud iam service-api-keys ([-a, --all], SERVICE_ID_NAME|SERVICE_ID_UUID) [-f, --force]



 Command options 

-a, --all
: Display all API keys that are associated with all services.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

-f, --force
: Display service API keys without confirmation.





 Examples 

List all API keys of service sample-service:

ibmcloud iam service-api-keys sample-service







 ibmcloud iam service-api-key 

List details of a service API key:

ibmcloud iam service-api-key (APIKEY_NAME|APIKEY_UUID) (SERVICE_ID_NAME|SERVICE_ID_UUID) [--uuid] [-f, --force]



 Command options 

APIKEY_NAME (required)
: Name of the API key, exclusive with APIKEY_UUID.

APIKEY_UUID (required)
: UUID of the API key, exclusive with APIKEY_NAME.

SERVICE_ID_NAME (required)
: Name of the service ID, exclusive with SERVICE_ID_UUID.

SERVICE_ID_UUID (required)
: UUID of the service ID, exclusive with SERVICE_ID_NAME.

--uuid
: Display the UUID of service API key.

-f, --force
: Display service API key without confirmation.





 Examples 

Show details of service API key sample-key of service sample-service:

ibmcloud iam service-api-key sample-key sample-service







 ibmcloud iam service-api-key-create 

Create a service API key:
* UI
* CLI
* API







 Listing and getting details of a linked zone 

List all linked zones and get the details of a linked zone by using the UI, CLI, or API.



 Listing a linked zone using the UI 

To list all linked zones using the UI, navigate to the Zones section of your DNS Services instance, then select the Linked zones tab.





 Getting the details of a linked zone using the UI 

To get the details of a linked zone using the UI, take the following steps:



1. Navigate to the Zones section of your DNS Services instance, then select the Linked zones tab.
2. Click the link in the Zone name column of the linked zone you want to view.



The Linked zone details page appears, where you can edit the linked zone details, [delete the linked zone](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-update-linked-zone), and manage permitted networks. For more information, see [Add a permitted network](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-add-permit-network-linked).





 Listing a linked zone using the CLI 

To list a linked zone using the CLI, run the following command:

ibmcloud dns cross-account linked-zones [-i, --instance INSTANCE] [--output FORMAT]

Where:



* -i, --instance value is the instance name or ID. If not set, the context instance specified by ibmcloud dns instance-target INSTANCE is used.
* --output value specifies the output format. Currently, json is the only supported format.







 Getting the details of a linked zone using the CLI 

To get the details of a linked zone using the API, run the following command:

ibmcloud dns cross-account linked-zone LINKED_ZONE_ID [-i, --instance INSTANCE] [--output FORMAT]

Where:



* LINKED_ZONE_ID is the ID of linked zone.
* -i, --instance value is the instance name or ID.
To restore a resource by using the API, call the [IBM Cloud® Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller?code=gorun-reclamation-action) as shown in the following example. Specify restore to restore a resource. id is the reclamation ID and not the resource instance ID.



* Curl
* Java
* Python
* Go
* Node



curl -X POST https://resource-controller.cloud.ibm.com/v1/reclamations/0114be9024c6eede47d08a85ac0c5c43/actions/restore -H 'Authorization: Bearer <IAM_TOKEN>' -H 'Content-Type: application/json' -d '{
"request_by": "bar",
"comment": "restore resource instance 614fc866-1d4f-4c9e-973e-637f1089a6a1"
}'

RunReclamationActionOptions runReclamationActionOptions = new RunReclamationActionOptions.Builder()
.id(reclamationId)
.actionName("restore")
.build();

Response<Reclamation> response = service.runReclamationAction(runReclamationActionOptions).execute();
Reclamation reclamation = response.getResult();

System.out.printf("runReclamationAction() response:n%sn", reclamation.toString());

reclamation = resource_controller_service.run_reclamation_action(
id=reclamation_id,
action_name='restore'
).get_result()

print('nrun_reclamation_action() response:n',
json.dumps(reclamation, indent=2))

runReclamationActionOptions := resourceControllerService.NewRunReclamationActionOptions(
reclamationID,
"restore",
)