vania-janet/multiturn-rag-retrieval-data huggingface dataset:
"collection_total" : 2
},
"resources" : [ {
"name" : "lock-1",
"description" : "lock for consumer-1",
"creation_date" : "2020-08-27T14:28:54Z",
"created_by" : "IBM-id-1",
"attributes" : {
"key" : "value"
},
"secret_version_id" : "5bf89b0c-df55-c8d5-7ad6-8816951c6784",
"secret_id" : "cb7a2502-8ede-47d6-b5b6-1b7af6b6f563",
"secret_group_id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
"last_update_date" : "2022-04-24T16:50:09.692573+03:00",
"secret_version_alias" : "current"
}, {
"name" : "lock-2",
"description" : "lock for consumer-2",
"creation_date" : "2020-08-27T14:29:01Z",
"created_by" : "IBM-id-1",
"attributes" : {
"key" : "value"
},
"secret_version_id" : "50277266-d706-4b3e-badb-f07257f8f581",
"secret_id" : "cb7a2502-8ede-47d6-b5b6-1b7af6b6f563",
"secret_group_id" : "bc656587-8fda-4d05-9ad8-b1de1ec7e712",
Are you getting an "not_found" error when updating settings? 

When updating settings, the following message is returned: Your request has failed because the target id target-logdna is not valid..

  What’s happening 

Your request fails with an error message and a code of not_found.

  Why it’s happening 

You are trying to update settings and have specified a target name for --default-targets instead of the target IDs.

  How to fix it 

Retry the request specifying the target IDs instead of the target names.
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:policy:06a40fd6-6fd7-460a-87d7-8388fc1be057",
"lastUpdateDate": "2020-06-18T20:35:41Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"interval_month": 2
}
}

 list the policies
$ ibmcloud kp key policies $KEY_ID --output json

[
{
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-18T20:35:41Z",
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:policy:06a40fd6-6fd7-460a-87d7-8388fc1be057",
"lastUpdateDate": "2020-06-18T20:35:41Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"interval_month": 2
}
}
]





 Required parameters 

KEY_ID
: The ID of the key that you want to query. To retrieve a list of your available keys, run the [kp keys](#kp-keys) command.





 Optional parameters
"rev": "13-bcb...29e"
}
],
"id": "ExampleID",
"seq": "5-g1A...HaA"
}
]
}









 Update validators 

Design documents with options.partitioned set to true can't contain a validate_doc_update field.

Update validators determine whether a document must be written to disk when insertions and updates are attempted. They don't require a query because they implicitly run during this process. If a change is rejected, the update validator responds with a custom error.

Update validators require four arguments:



Table 3. Arguments for the update validator

 Argument Purpose 

 newDoc The version of the document passed in the request. 
 oldDoc The version of the document currently in the database, or null if none exists. 
 secObj The [security object](https://cloud.ibm.com/apidocs/cloudantgetsecurity) for the database. 
 userCtx Context regarding the currently authenticated user, such as name and roles. 



Update validators don't apply when a design document is updated by an admin user. This practice ensures that admins can never accidentally lock themselves out.

See the following example design document with an update validator:

{
"_id": "_design/validator_example",
"validate_doc_update": "function(newDoc, oldDoc, userCtx, secObj) { ... }"
}

See the following example of an update validator:

function(newDoc, oldDoc, userCtx, secObj) {
if (newDoc.address === undefined) {
throw({forbidden: 'Document must have an address.'});
}
}

See the following example response from an update validator:

{
"error": "forbidden",
"reason": "Document must have an address."
}





 Retrieving information about a design document
[Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/icons/actions-icon-vertical.svg) in the row for the account group, and select Edit.
3. Select the new contact for the account group, and click Save.







 Updating the account group contact by using the CLI 

This action can be done only through the UI, API, or SDKs. To see the steps, switch to the UI or API instructions.





 Updating the account group contact by using the API 

To update the primary contact for the account group, call the [Enterprise Management API](https://cloud.ibm.com/apidocs/enterprise-apis/enterpriseimport-an-account-into-an-enterprise) as shown in the following sample request. Replace the IAM token and ID variables with the values from your enterprise.



1. If a user that you want to assign as the contact isn't in the enterprise, first invite the user to the enterprise account. See [Inviting users](https://cloud.ibm.com/docs/account?topic=account-iamuserinv) for more information.
2. Update the primary contact by passing the IAM ID of the user that you want to be the new primary contact for the enterprise.





* Curl
* Java
* Python
* Go
* Node



curl -X PATCH "https://enterprise.cloud.ibm.com/v1/account-groups/$ACCOUNT_GROUP_ID" -H "Authorization: Bearer <IAM_Token>" -H 'Content-Type: application/json' -d '{
"primary_contact_iam_id": "enterpriseAccountIamId"
}'

UpdateAccountGroupOptions updateAccountGroupOptions = new UpdateAccountGroupOptions.Builder()
.accountGroupId(accountGroupId)
.name("Updated Example Account Group")
Follow the Veeam instructions at [Updating license](https://helpcenter.veeam.com/docs/backup/vsphere/license_update.html).





 Updating Veeam licenses for instances that are deployed as a bare metal server or VSI, or deployed as a VM with private network only 

If the Veeam service is deployed on an instance as a bare metal server or VSI, or is deployed as a VM with private network only, take note of the expiration date for your license. When renewal is needed, [contact IBM® Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support) to get assistance with updating the license key.





 Known issue about license key message for automatic updating 

On the Veeam console, when you’re automatically updating a license before it expires, you might see a License key is up-to-date message that looks like an error. You can ignore the message because it's not an error.







 Related links 



* [Veeam Backup and Replication 12 overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview)
* [Ordering Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_ordering)
* [Ordering Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_ordering_licenses)
* [Managing Veeam licenses](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam_managing_licenses)
* [Ordering and configuring IBM Cloud Object Storage with Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-icos_ordering)
If you used the default bulk transaction mode, then the new revision wasn't created. You must resubmit the document to the database.

Conflict resolution that uses the bulk docs interface is identical to the resolution procedures outlined in the [Conflicts](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-conflicts) documentation.





 forbidden 

Entries with this error type indicate that the validation routine that was applied to the document during submission returned an error.

See an example JavaScript to produce forbidden error as part of a validation function:

throw({forbidden: 'invalid recipe ingredient'});

See an example error message from a validation function:

{
"id" : "7f7638c86173eb440b8890839ff35433",
"error" : "forbidden",
"reason" : "invalid recipe ingredient"
}







 The _bulk_get endpoint 

You might need to access all the available information about multiple documents. The _bulk_get endpoint is similar to the [_all_docs](https://cloud.ibm.com/apidocs/cloudantpostalldocs) endpoint, but returns information about the requested documents only.

Like the _bulk_docs endpoint, a JSON document that is supplied in the request includes an array that identifies all the documents of interest.

See an example of using HTTP to run the bulk GETrequest of document information:

POST /$DATABASE/_bulk_get HTTP/1.1
Accept: application/json

See an example of using the command line to run the bulk GETrequest:



* Curl
* Java
* Python
* Go
* Node



curl -H "Authorization: Bearer $API_BEARER_TOKEN" -X POST "$SERVICE_URL/orders/_bulk_get" -H "Content-Type: application/json" --data '{
"docs": [
{
"id": "order00067",
"rev": "3-917fa2381192822767f010b95b45325b"
For a practical example of how to implement these changes, see [this project with sample code](https://github.com/glynnbird/deconflict).





 Upload the new revision 

See the following final revisions after you resolve and merge changes from the previous conflicting revisions:

{
"_id": "74b2be56045bed0c8c9d24b939000dbe",
"_rev": "3-daaecd7213301a1ad5493186d6916755",
"name": "Samsung Galaxy S4",
"description": "Latest smartphone from Samsung",
"price": 600
}

After you assess and resolve the conflicts, you create a document that includes the current and definitive data. This fresh document is uploaded into the database.





 Delete old revisions 

See the following example requests to delete the old revisions:

DELETE https://$ACCOUNT.cloudant.com/products/$_ID?rev=2-61ae00e029d4f5edd2981841243ded13

DELETE https://$ACCOUNT.cloudant.com/products/$_ID?rev=2-f796915a291b37254f6df8f6f3389121

In the final step, you delete the old revisions. You delete the old revisions by sending a DELETE request, specifying the revisions to delete.

When the older versions of a document are deleted, the conflicts that are associated with that document are marked as resolved. You can verify that no conflicts remain by requesting the document again. Set the conflicts parameter to true, and use [find conflicts](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-conflictsfinding-conflicts) as before.
"crn": "crn:v1:bluemix:public:kms:us-south:a/e3e8fd14a61a49cda102faad15b06c09:5ecfe306-d4af-48c0-ab07-b5c5bc751534:policy:0ec7ad62-982d-45bb-895f-986d95015f5b",
"lastUpdateDate": "2022-12-02T00:51:38Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"enabled": true,
"interval_month": 3
}
}
---------------------------------------------------------------------------------------------------------------------------------------------------
Show more

 disable the policy for this key

ibmcloud kp key policy-update rotation 4d5540bd-3235-4a46-a8af-974f7ed6558a -d --output json

{
"createdBy": "user id ...<redacted>...",
"creationDate": "2022-12-02T00:50:11Z",
"messageid": "M1008",
"message": "Bad request. Check that the information you entered in the payload is complete and formatted correctly in JSON.",
"statuscode": 400
}

 How to fix it 

Verify your CURL or the payload contains that the location and the url are pointing to the same region where you want to create or update the workspace.

For example



* For creating workspace in US region: Use location as us-east or us-south and url as https://us-south.schematics.cloud.ibm.com/ or https://us-east.schematics.cloud.ibm.com/. By default https://cloud.ibm.com/schematics/workspaces points to https://cloud.ibm.com/schematics/overview endpoint.
* For workspace in the EU region: Use location as eu-de or eu-gb and url as https://eu-de.schematics.cloud.ibm.com and https://eu-gb.schematics.cloud.ibm.com endpoint.
"backup_id": "crn:v1:bluemix:public:databases-for-mysql:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6",
"version":8
}'





 Upgrading through the API 

Complete the necessary steps to use the [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controllercreate-resource-instance) before using it to upgrade from a backup. Then, send the API a POST request. The parameters name, target, resource_group, and resource_plan_id are all required. You also supply the version and backup_ID. The new deployment has the same memory and disk allocation as the source deployment at the time of the backup.

curl -X POST https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "my-instance",
"target": "bluemix-us-south",
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "databases-for-mysql-standard",
Follow the same processes that are described in steps [2](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-msp) - [7](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-channel) to update the admin certificate in the MSP, peer, orderer, and channel. If any of the channel member or channel orderer organization admin certs have expired, then you also need to [override the orderer configuration to allow expired certs for channel updates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtibp-console-identities-expired-certs-orderer-override).







 Bulk admin certificate renewal with Ansible playbooks 

If your network contains a large number of channels that need to be updated, or if you prefer to automate the process of updating the peer organization MSP or orderer organization MSP on the ordering service, system channel, and application channel, a set of Ansible playbooks is available to script this process. These playbooks can only be used if the certificates have not expired. See the playbooks under [Adding an administrator certificate](https://ibm-blockchain.github.io/ansible-collection/tasks/addadmincert.html) for instructions.





 Expired certificates 

When certificates expire, it is likely that peer, orderer, and channel operations will fail, but it is still possible to update the certificates. The process to address them depends on whether they are MSP admin certificates or enrollment certificates.



 How to fix expired organization admin certificates 

If the peer or orderer organization admin certificates have expired, you need to generate certificates for a new admin identity. The overall process depends on whether Node OU is enabled for the MSP that the admin certificate belongs to.

Register a new user and enroll the identity for a new peer organization or orderer organization admin identity with the same CA that the existing peer or orderer organization admin was registered with.



1.
The ibmUniqueId field shows the ID of the user that matched the event initiator.name field. The email field shows the email address associated with that ID.



To get the API key on which the action has been requested and failed, see the field prev_instance_name in requestData.





 Resource is locked. Request to update Service ID or API key fails 

When a service ID or an API key are locked, you cannot change any of its attributes. The event that is generated has an outcome of failure.

Depending on the resource type, you can get any of the following messages:



* Service ID: The message that you get says IAM Identity Service: update account-serviceid ServiceIDName -failure where ServiceIDName is the name of the service ID.
* User API key: The message that you get says IAM Identity Service: update user-apikey APIkeyName -failure where APIkeyName is the name of the API key.
* Account API key: The message that you get says IAM Identity Service: update account-apikey APIkeyName -failure where APIkeyName is the name of the API key.



In the event, the lock field in requestData is set to true. This is the reason why this action fails. To successfully change an attribute of a service ID, the lock field must be set to false.

Notice that the field severity is set to critical. Someone is trying to modify a service ID that is locked in the account.
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:key:c024c2b3-2093-46e5-aabb-fdf8cbc14e44"
}

 update the policy and rotate the key every 2 months
$ ibmcloud kp key policy-update rotation $KEY_ID -m 2 --output json

{
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-18T20:35:41Z",
"crn": "crn:v1:bluemix:public:kms:us-south:a/ea998d3389c3473aa0987652b46fb146:a192d603-0b8d-452f-aac3-f9e1f95e7411:policy:06a40fd6-6fd7-460a-87d7-8388fc1be057",
"lastUpdateDate": "2020-06-18T20:35:41Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"interval_month": 2
}
}

 list the policies
$ ibmcloud kp key policies $KEY_ID --output json

[
{
"createdBy": "user id ...<redacted>...",
"creationDate": "2020-06-18T20:35:41Z",
* [Step four: Update peer organization MSP on application channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-channel-peer)
* [Step five: Update channel member on ordering service system channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-os-channel-member)
* [Step six: Update ordering service admin on ordering service system channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-os-admin)
* [Step seven: Update orderer organization MSP on channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-channel)



* [Certificates from an external CA](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-ext-ca)



* [Peer and ordering node enrollment and TLS certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-ext-ca-enrollment-tls)
* [Peer and ordering node organization admin certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-ext-ca-admin)



* [Bulk admin certificate renewal with Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-bulk-ansible)
* [Expired certificates](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtibp-console-identities-expired-certs)
},
"metrics": {
"provider": "prometheus",
"statsd": {
"network": "udp",
"address": "127.0.0.1:8125",
"writeInterval": "10s",
"prefix": "server"
}
}
}
}
Show more

Paste the modified JSON that contains only the parameters that you want to update into the Configuration JSON box. For example, if you only needed to update the value for the passwordattempts field you would paste in this JSON:

{
"ca": {
"cfg": {
"identities": {
"passwordattempts": 3
}
}
}
}

If you need to enable deletion of registered users from a CA you would insert "allowremove": true into the JSON as follows:

{
"ca": {
"cfg": {
"identities": {
"passwordattempts": 10,
"allowremove": true
}
}
}
}

The ability to update a CA configuration is not available for CAs that have been imported into the console.









 Peer deployment 

When you deploy a peer, the following advanced deployment options are available:



* [State database](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-level-couch) - Choose the database for your peers where ledger transactions are stored.
* [Deployment zone selection](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-peer-k8s-zone) - In a multi-zone cluster, select the zone where the node is deployed.
The bulk document update procedure is similar to the insertion procedure, except that you must specify the document ID and current revision for every document in the bulk update JSON string.

See an example of using HTTP to do a bulk update:

POST /$DATABASE/_bulk_docs HTTP/1.1
Accept: application/json

See an example of using the command line to do a bulk update:



* Curl
* Java
* Python
* Go
* Node



curl -H "Authorization: Bearer $API_BEARER_TOKEN" -X POST "$SERVICE_URL/events/_bulk_docs" -H "Content-Type: application/json" --data '{ "docs": [ { "_id": "0007241142412418284", "type": "event", "userid": "abc123", "eventType": "addedToBasket", "productId": "1000042", "date": "2019-01-28T10:44:22.000Z" }, { "_id": "0008001142412418285", "type": "event", "userid": "def456", "eventType": "addedToBasket", "productId": "1000043", "date": "2019-01-28T12:30:00.000Z" } ], "new_edits": true }'

import com.ibm.cloud.cloudant.v1.Cloudant;
import com.ibm.cloud.cloudant.v1.model.BulkDocs;
import com.ibm.cloud.cloudant.v1.model.Document;
import com.ibm.cloud.cloudant.v1.model.DocumentResult;
import com.ibm.cloud.cloudant.v1.model.PostBulkDocsOptions;

import java.util.Arrays;
import java.util.List;

Cloudant service = Cloudant.newInstance();

Document eventDoc1 = new Document();
"collectionTotal": 2
},
"resources": [
{
"id": "02fd6835-6001-4482-a892-13bd2085f75d",
"type": "application/vnd.ibm.kms.key+json",
"name": "Root-key",
"state": 1,
"crn": "crn:v1:bluemix:public:kms:us-south:a/f047b55a3362ac06afad8a3f2f5586ea:12e8c9c2-a162-472d-b7d6-8b9a86b815a6:key:02fd6835-6001-4482-a892-13bd2085f75d",
"createdBy": "...",
"creationDate": "2020-03-11T16:30:06Z",
"lastUpdateDate": "2020-03-11T16:30:06Z",
"algorithmMetadata": {
"bitLength": "256",
"mode": "Deprecated"
},
"extractable": false,
"imported": true,
"algorithmMode": "Deprecated",
"algorithmBitSize": 256,
"dualAuthDelete": {
"enabled": false
}
},
{
"id": "2291e4ae-a14c-4af9-88f0-27c0cb2739e2",
"type": "application/vnd.ibm.kms.key+json",
"name": "Standard-key",
"state": 1,
"expirationDate": "2020-03-14T03:50:12Z",
The channel update policy is updated to remove your organization automatically. When you are ready, click Update channel to submit a channel update request. The request starts the [process for collecting the signatures](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-signature-collection) that are required to update the channel, depending on your update policy.

After you remove your organization from the channel, you can delete your peers on the IBM Blockchain Platform. If transactions can be successfully submitted to the network after you remove your peers, your organization is no longer required to endorse transactions.
2. Have your organization removed from the consortium hosted by the ordering service. After you are removed from the consortium, your organization can no longer be added to new channels. This action needs to be completed by an ordering service administrator.

Navigate to the Nodes tab and click the ordering service of your network. On the ordering service panel, find the organization to be removed in the list of Consortium members. Click the Delete button in the corner of the organization MSP definition tile.
3. Delete your ordering nodes. If you operate ordering nodes that are part of a multi-node ordering service, you need to remove your ordering nodes from the network before you remove your ordering organization. Your ordering nodes need to be removed from the consenter set of each channel before they are removed from the ordering service.

Navigate to the Channels tab and click the Settings icon to update the channel. You can use the Consenter Set section to remove your ordering node from the channel. When you are ready, click Update channel to submit the channel update request. The update request starts the [process for collecting the signatures](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-update-channel-signature-collection) that are required to update the channel, depending on the channel update policy. After you have you removed your ordering nodes, you can use the Ordering service administrators section to remove your organization from the set of orderer administrators.
I fixed an issue, why weren't my results updated? 

  What’s happening 

You fixed an issue that was flagged by Security and Compliance Center and then reran a scan, but your results weren't updated.

  Why it’s happening 

This issue is caused by a cache. When an scan is run, the results for your account are cached for an hour.

  How to fix it 

To resolve the issue, wait one hour between scans.