vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"tag": "example.com:ed10e4b2-8a64-4afa-a4e2-9e60a766d079"
},
"errors": [],
"messages": []
}

For future reference, the "id" in response is used as DNSZONE_ID.







 Getting a DNS zone 

Use the following command to get an existing zone.



 Request getting a DNS zone 

curl -X GET $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID -H "Authorization: $TOKEN"





 Response to getting a DNS zone 

{
"success": true,
"result": {
"id": "example.com:ed10e4b2-8a64-4afa-a4e2-9e60a766d079",
"created_on": "2019-07-24 12:30:58.357201205 +0000 UTC",
"modified_on": "2019-07-24 12:30:58.357201205 +0000 UTC",
"instance_id": "1a34bda8-9c94-4232-bea7-7df163b21d23",
"name": "example.com",
"description": "Example zone",
"state": "PENDING_NETWORK_ADD"
},
"errors": [],
"messages": []
}







 Updating a DNS zone 

Use the following command to update an existing zone. You can update the description and label fields. All other fields are read-only.



 Request update a DNS zone 

curl -X PATCH $DNSSVCS_ENDPOINT/v1/instances/$INSTANCE_ID/dnszones/$DNSZONE_ID -H 'Content-Type: application/json' -H "Authorization: $TOKEN" -d '{
When you provision an instance from an image that belongs to another account or from an instance template that specifies such an image, the image still belongs to the other account even though the instance belongs to your account. A reference to such an image might exist in details of the instance and related resources. For example, details about its boot volume and any snapshot that was created from that boot volume might reference that image. Regardless of your authorizations, you can't access this type of custom image by its ID and attempts fail as if the image does not exist.

Image references are used in a few different places in the CLI. For example, if you use the ibmcloud is instance command to retrieve instance data, you see the following within the output.

Image ID Name
r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999 test-image

If you try to retrieve information about this image by using its ID,

ibmcloud is image r006-6cab2dbd-4e57-4dc5-810b-b7366cb78999

then this attempt fails with an error such as the following example:

FAILED
Response HTTP Status Code: 404
Error code: not_found
Error message: The requested resource does not exist, or cannot be accessed.
Error target name: id, type: parameter
Trace ID: d8b4d382-2993-4a89-a371-1db991b510d8

This error means that the image doesn't exist in your account. If the instance was provisioned by using a shared catalog image in another account, this output is the output that you always see even if the image exists in the owning account.

Additionally, it is possible that the referenced image might have the same name as a custom image in your account. But these image names are for two different images in two different accounts. While the CLI uses both ID and Name to identify an image, only the ID uniquely identifies an image across IBM Cloud®.
In the following endorsement policy example, peers who are members of org1msp can endorse transactions if their enroll id was registered with the type of client, peer, orderer, or admin. However, for peers who are members of org2msp, their enroll id must have been registered with a type of peer to be able to endorse transactions. The OutOf expression indicates that 1 out of the 2 organizations must endorse the transaction.

OutOf(1, 'org1msp.member', 'org2msp.peer')

Unsure which type was selected when a peer identity was registered? From the console, you can open the CA where the peer identity was registered and view the list of registered users and their associated type.







 Versioning a smart contract 

It is likely that you will need to modify the smart contract over time as channel members agree to changes in the business logic. Or, your organization may prefer to implement certain aspects of the logic according to your business needs. Regardless, the platform recommends using the following convention:

In order to facilitate the smart contract versioning process, package naming should be of the format:
[SMART_CONTRACT_NAME]_[VERSION]

where[VERSION] contains:



* n.n when the version requires approval across organizations in the channel. For example, mysmartcontract_1.0.
* n.n.n when the version does not require approval from other organizations on a channel. For example, mysmartcontract_1.0.1. Note that this updated version of the smart contract package cannot introduce any modifications the to read/write set that could cause transaction endorsement to fail. Use this option to incrementally patch your smart contract as needed. This means organizations can roll out minor fixes, for example slight variations such as error checking, to the smart contract independent of other organizations. The important thing is that always, the smart contract must implement the same reads and the same writes to the ledger across all organizations.



Although this recommended convention is not enforced by Fabric, it provides a standard nomenclature for you to update the smart contract on your organization's peers without requiring approval from other channel members.
Do not delete these add-on resources.

kubectl apply -f <app_ingress_resource>.yaml -n namespace
7. Verify that App ID authentication is enforced for your apps.



* If your apps supports the [web app strategy](https://cloud.ibm.com/docs/appid?topic=appid-key-conceptsterm-web-strategy): Access your app's URL in a web browser. If App ID is correctly applied, you are redirected to an App ID authentication log-in page.
* If your apps supports the [API strategy](https://cloud.ibm.com/docs/appid?topic=appid-key-conceptsterm-api-strategy): Specify your Bearer access token in the Authorization header of requests to the apps. To get your access token, see the [App ID documentation](https://cloud.ibm.com/docs/appid?topic=appid-obtain-tokens). If App ID is correctly applied, the request is successfully authenticated and is routed to your app. If you send requests to your apps without an access token in the Authorization header, or if the access token is not accepted by App ID, then the request is rejected.



8. Optional: You can customize the default behavior of the OAuth2-Proxy by creating a Kubernetes ConfigMap.



1. Create a ConfigMap YAML file that specifies values for the OAuth2-Proxy settings that you want to change.

apiVersion: v1
kind: ConfigMap
metadata:
name: oauth2-<App_ID_service_instance_name>
namespace: <ingress_resource_namespace>
data:
auth_logging: <true|false>
 Log all authentication attempts.
auth_logging_format:
 Format for authentication logs. For more info, see https://oauth2-proxy.github.io/oauth2-proxy/configurationauth-log-format
cookie_csrf_expire: "15m"
If you have selected only one of these two roles (Reader or Object Writer) during the service to service authorization, you may endup with not able to write or read from the IBM Cloud Object Storage bucket. You will get an error for service to service authorization failure in these cases. Make sure to recreate an authorization between the services with both the roles selected.
9. Click Authorize.







 Creating an authorization by using the CLI 

To authorize a source service to access a target service, run the ibmcloud iam authorization-policy-create command.

For more information about all of the parameters that are available for this command, see [ibmcloud iam authorization-policy-create](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_iamibmcloud_iam_authorization_policy_create).







 How to find the Bucket name in the IBM Cloud Object Storage service instance? 



1. Login to your IBM Cloud account.
2. Navigate to Resource List in the menu.
3. Navigate to Storage in the Resource list.
4. Click the IBM Cloud Object Storage name that will display your IBM Cloud Object Storage console.
5. In the IBM Cloud Object Storage console, navigate to Buckets.
6. Select and copy the required Bucket name that need to used in the destination creation process. Use this copied Bucket name in the destination creation screen.







 How to find the Endpoint URL of the IBM Cloud Object Storage service instance? 

Endpoints are used with your credentials (Bucket name, API Key, SDK) to tell your service where to look for your bucket.



1. Login to your IBM Cloud account.
2. Navigate to Resource List in the menu.
3. Navigate to Storage in the Resource list.
4. Click the IBM Cloud Object Storage name that will display your IBM Cloud Object Storage console.
5. In the IBM Cloud Object Storage console, navigate to Buckets in the menu.
6. Click the required Bucket name to view the Bucket configuration details.
7.