vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information about available command options, see [ibmcloud is backup-policy-update](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policy-update).





 Updating a backup plan from the CLI 

Run the ibmcloud is backup-policy-plan-update command to update a backup plan. Identify the policy and plan by ID or name in the command line. You can update the plan name, cron-spec backup schedule, attach user tags, update backup retention period, add, or remove fast restore zones.

The following code snippet shows the command syntax.

ibmcloud is backup-policy-plan-update POLICY PLAN --cron-spec CRON_SPEC [--name NAME] [--active] [--attach-tags ATTACH_TAGS] [--copy-tags true | false] [--delete-after DELETE_AFTER] [--delete-over-count DELETE_OVER_COUNT] [--clone-policy-zones ZONES] [--clone-policy-max-snapshots MAX_SNAPSHOTS] [--output JSON] [-q, --quiet] [--copy-remote-regions TBD] [--encryption-key TBD]

To rename the backup plan, run the command like the following example. It specifies the backup policy and plan by name, and changes the name of the plan from my-policy-plan-c to my-policy-plan-b.

cloudshell:$ ibmcloud is backup-policy-plan-update new-policy-23 my-policy-plan-c --name my-policy-plan-b
Updating plan my-policy-plan-c of the backup policy r138-0521986d-963c-4c18-992d-d6a7a99d115f under account Test Account as user test.user@ibm.com...

ID r138-6f4f08ba-e0bb-470f-bbfb-f3a22aebbfa9
Name my-policy-plan-b
Active true
Lifecycle state updating
For more information about available command options, see [ibmcloud is backup-policy-update](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policy-update).





 Editing tags for target resources from the CLI 

Run the ibmcloud is backup-policy-update command and specify the policy ID or policy name, and the tags that you want to modify.

ibmcloud is backup-policy-update POLICY [--match-tags MATCH_TAGS] [--output JSON] [-q, --quiet]

The following example updates backup policy user tags of the policy that is identified by ID.

cloudshell:$ ibmcloud is backup-policy-update r138-0521986d-963c-4c18-992d-d6a7a99d115f --match-tags dev:env,bck:test
Updating backup policy r138-0521986d-963c-4c18-992d-d6a7a99d115f under account Test Account as user test.user@ibm.com...

ID r138-0521986d-963c-4c18-992d-d6a7a99d115f
Name new-policy-23
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::backup-policy:r138-0521986d-963c-4c18-992d-d6a7a99d115f
Status stable
Last job completed at 2023-02-22T20:12:44.000Z
Plans ID Name Resource type
r138-2129a79a-5629-4069-bf79-7bb0af3b0bd3 my-policy-plan-a backup_policy_plan
The following example renames a backup policy that is identified by name:

cloudshell:$ ibmcloud is backup-policy-update backup-policy-v1 --name new-policy-23
Updating backup policy backup-policy-v1 under account Test Account as user test.user@ibm.com...

ID r138-0521986d-963c-4c18-992d-d6a7a99d115f
Name new-policy-23
CRN crn:v1:bluemix:public:is:eu-de:a/a10d63fa66daffc9b9b5286ce1533080::backup-policy:r138-0521986d-963c-4c18-992d-d6a7a99d115f
Status stable
Last job completed at 2023-02-22T20:12:44.000Z
Plans ID Name Resource type
r138-2129a79a-5629-4069-bf79-7bb0af3b0bd3 my-policy-plan-a backup_policy_plan
r138-6f4f08ba-e0bb-470f-bbfb-f3a22aebbfa9 my-policy-plan-c backup_policy_plan

Backup tags dev:test
Backup resource type volume
Resource group defaults
Created at 2023-02-21T22:42:10+00:00

For more information about available command options, see [ibmcloud is backup-policy-update](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencebackup-policy-update).





 Editing tags for target resources from the CLI 

Run the ibmcloud is backup-policy-update command and specify the policy ID or policy name, and the tags that you want to modify.

ibmcloud is backup-policy-update POLICY [--match-tags MATCH_TAGS] [--output JSON] [-q, --quiet]
Controlling user visibility 

There are two ways to change how a user views other users in an account. The first is by using the user list visibility setting. And, the second is for classic infrastructure users, and it is directly related to the parent user that is listed. The assigned parent user determines which users a specific user can view when the setting for user list visibility is enabled.



  Setting user view access 

As an IBM Cloud® account owner, you can view all users in your account and define how users can view other users in the account. By using the user list visibility setting, you can control how users see others across the account.

When the setting is disabled, any user in the account can view other users from the Users page in IBM Cloud console. When the setting is enabled, users can view only specific types of users in the account:



*  Users invited by the user
*  Users who are their descendants in the classic infrastructure user hierarchy, meaning the users that they invited or that one of their descendants invited.



By default, the setting is disabled for your account. To update this setting, complete the following steps:



1.  In the IBM Cloud console, click Manage > Access (IAM), and select Settings.
2.  From the Account section, enable the User list visibility setting.
3.  Click Yes to confirm.







  Updating a user's parent user 

If you have the correct access, you can update the parent for a user. Updating the parent user affects how a user views other users in the account when the setting for user list visibility is enabled. Users can view only other users for which they are a parent and any other users who are invited by those descendants of the parent user.

If you have the following access, you can update the parent for another user:



*  An IAM policy with Editor or higher role on the User management service.
*  You are an ancestor in the classic infrastructure hierarchy for the user and you have the Manage user classic infrastructure permission assigned.



To update a user's parent, complete the following steps:



1.  In the IBM Cloud console, click Manage > Access (IAM), and select Users.
2.  Select a user's name from the list.
3.  From the User details page, select a new parent user from the Parent menu.
4.  Click Apply.
In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select your product.
3. Click Edit company in the Company section.
4. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg).
5. Enter the legal name of your company, and click Save.







 Updating your company information by using the API 

You can programmatically update your company details 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 updates the company name to My updated company:

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 '{
"provider": "My updated company"
}'





 Updating your product information by using the console 



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select your product.
3.
* Subscribed Apps
* Apps per Plan
* Success Rate
* API Calls per Day



Tip When you select each visualization, the selection tab blocks your dashboard view, so you may not realize that the visualization was added to the dashboard. Select one visualization at a time and close the selection tab each time to see the changes to your dashboard.
3. Click Save and give your dashboard a name: Subscriber Dashboard.

![savedashboard.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/savedashboard.png)

![namedashboard.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/namedashboard.png)







 Activity 4: Creating new visualizations 

On the Subscriber Dashboard that we created, we included the built-in visualization that shows API Calls per Day. When we look at all of that information presented together, we'd really like to see the usage by App. Let's create a new visualization that shows this information.



1. Click New Visualization and select the Create Visualizations link. ![newvisualization.png](https://cloud.ibm.com/docs-content/v1/content/78bb71851d95d7580503eb9ba10cf3ae31490ade/apiconnect/tutorials/images/newvisualization.png)
2. Select Line chart as your visualization type. The initialized line chart has the Y-Axis setup with a count of API calls. This is appropriate for our chart.
3. Select the following:



* Buckets type: X-Axis
* Aggregation: Date Histogram
* Custom Label: Time



4.
<-- </section "class="ph" id="section-baas-view-plan-fast-restore" "> --><-- <section "class="ph" id="section-baas-view-plan-crc" "> --> Retrieving a backup plan with the cross-regional copy option NewMake a GET /backup_policy/{backup_policy_id}/plans/{plan_id} call. In the response, the remote_region_policies property shows the remote region where a copy of the backup is created.See the following example. curl -X GET "$vpc_api_endpoint/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f/plan/4d58eb08-d950-498b-8175-b4d617b6ba6a?version=2023-05-09&generation=2" ?version=2023-05-09&generation=2"
-H "Authorization: $iam_token"
The response shows the remote region policy information. In this example, the output shows that when the backup job creates a backup snapshot in the us-south region, a copy of the backup is created in the us-east region, too. {
"active": true,
"attach_user_tags":
"hourly-backups"
],
"copy_user_tags": false,
"created_at": "2023-05-09T15:16:37Z",
"cron_spec": "0 /2 * * ",
"deletion_trigger": {
"delete_after": 5
},
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.







 Upgrading a smart contract 

You can upgrade a smart contract to change its code, endorsement policy, or private data collection while maintaining its relationship to the assets on the ledger. There are a variety of reasons why you may want to upgrade an instantiated smart contract.



1. You can upgrade the smart contract to add or remove functionality from its code and iterate on the logic of your business network.
2. Whenever a new member is added to a channel, the endorsement policy of the instantiated smart contracts must be updated to include the new channel member. In order to work with the new channel member, the smart contract must be repackaged with a new version number and instantiated on the channel, even if the smart contract itself is unchanged. Otherwise, transaction endorsement cannot succeed.
3. When a private data collection has changed, for example an organization is added or removed you need to upgrade your smart contract. Or, use this action whenever a new private data collection is added to the collection configuration JSON file.
4. The smart contract initialization arguments have changed.



Before you upgrade an instantiated smart contract, the new version of the smart contract must be installed on all peers in the channel that are running the previous level of the smart contract.

Be aware that after you have upgraded your peers to the v2.x image and switched your application channel capability to 2.0, you can no longer upgrade your smart contract using the instructions in this topic. Instead, you need to repackage your smart contract and [deploy the smart contract on the network using Fabric v2.x](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2).



 How to upgrade a smart contract 

To upgrade a smart contract, install the updated code by specifying the same smart contract name but by using and a new version number. If you have installed a newer version of a smart contract on any peer in the channel, notice that the original version now has the Upgrade Available button next to it in the Instantiated smart contracts table.
_settings](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/iam_account_settings)<br> * [ibm_cm_catalog](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cm_catalog)<br> * [ibm_cm_offering](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cm_offering)<br> * [ibm_cm_offering_instance](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cm_offering_instance)<br> * [ibm_cm_version](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/cm_version)<br> * [ibm_enterprises](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/enterprises)<br> * [ibm_enterprise_accounts](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/enterprise_accounts)<br> * [ibm_enterprise_account_groups](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/enterprise_account_groups)<br><br><br> <br><br> * Latest [version change log](https://github.com/IBM-Cloud/terraform-provider-ibm/releases/tag/v1.23.0)<br><br><br> 







 1 April 2021 



 New resources New data sources Enhancements
In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. Select your product.
3. Click Dashboard.
4. To update the name of the product, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/edit-tagging.svg). Make sure that your product name meets the following requirements:



* Use 60 characters or less.
* Do not include the name of the company, any former product names, or details such as deployment target, method, or pricing. You can include this information in your readme file.
* Do not include "IBM Cloud".









 Updating your product information by using the API 

You can programmatically update your product details by calling the [Partner Center Sell API](https://cloud.ibm.com/apidocs/partner-center-sellupdate-product) as shown in the following sample request. The example updates the name of the product to My updated product:

curl --request PATCH --url https://product-
lifecycle.api.cloud.ibm.com/openapi/v1/products/9fab83da-98cb-4f18-
a7ba-b6f0435c9673 --header 'Authorization: Bearer TOKEN' --header 'Content-Type: application/json' --data '{
"productName": "My updated product",
"materialAgreement": true,
"taxAssessment": "SOFTWARE",
}'

The name of the product (productName) is displayed to users when you publish your product in the catalog.
"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 

Make a GET /backup_policies/{backup_policy_id}/plans request to list the plans that are associated with a backup policy. You can have up to four plans per policy. See the following example.

curl -X GET "$vpc_api_endpoint/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f/plans?version=2022-12-16&generation=2" -H "Authorization: $iam_token"

A successful response looks like the following example.

{
"plans": [
{
"active": true,
"attach_user_tags":
"my-daily-backup-plan"
],
"copy_user_tags": true,
"created_at": "2022-12-16T00:45:28.421Z",
"cron_spec": "/5 1,2,3 * * ",
"deletion_trigger": {
"delete_after": 20
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/backup_policies/fb721535-2cc6-45d6-ade7-3ceb95b7f26f/plans/4cf9171a-0043-4434-8727-15b53dbc374c",
'packageId': package_id,
'useHourlyPricing': True, Required since LBaaS is an hourly service
'prices': [{'id': price_id} for price_id in prices],
'protocolConfigurations': protocols,
'subnets': [{'id': subnet_id}],
'useSystemPublicIpPool': False,
'type': 1, public to private load balancer
'publicSubnets': [{'id': publicSubnet_id}]
}

try:
 If verify=True it checks your order for errors.
 It orders the lbaas if False.
if verify:
response = self.client['Product_Order'].verifyOrder(orderData)
else:
response = self.client['Product_Order'].placeOrder(orderData)

return response
except SoftLayer.SoftLayerAPIError as e:
print("Unable to place the order: %s, %s" % (e.faultCode, e.faultString))
...
Show more





 Retrieving details on load balancers 



 List all load balancers 

import SoftLayer
from prettytable import PrettyTable

class LBaasExample():
def __init__(self):
client = SoftLayer.Client()
self.lbaas_service = client['Network_LBaaS_LoadBalancer']

def get_list(self, dc=None):
_filter = None
lbaas_list = None

 Use filters if datacenter is set
if dc:
_filter = {"datacenter":{"name":{"operation": dc}}}

try:
 Retrieve load balancer objects
lbaas_list = self.lbaas_service.getAllObjects(filter=_filter)
except SoftLayer.SoftLayerAPIError as e:
Audit and Accountability (AU) [AU-3 Content of Audit Records](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-3) <br>[AU-4 Audit Log Storage Capacity](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-4) <br>[AU-5 Response to Audit Processing Failures](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-5) <br>[AU-6 Audit Record Review, Analysis. and Reporting](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6) <br>[AU-6 (1) Audit Record Review, Analysis. and Reporting | Automated Process Integration](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6.1) <br>[AU-7 Audit Record Reduction and Report Generation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-7) <br>[AU-10 Non-repudiation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-10) <br>[AU-11 Audit Record Retention](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-11) 



3. Upgrade your account to either Pay-As-You-Go or Subscription. For more information, see [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).
Audit and Accountability (AU) [AU-3 Content of Audit Records](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-3) <br>[AU-4 Audit Log Storage Capacity](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-4) <br>[AU-5 Response to Audit Processing Failures](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-5) <br>[AU-6 Audit Record Review, Analysis. and Reporting](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6) <br>[AU-6 (1) Audit Record Review, Analysis. and Reporting | Automated Process Integration](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6.1) <br>[AU-7 Audit Record Reduction and Report Generation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-7) <br>[AU-10 Non-repudiation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-10) <br>[AU-11 Audit Record Retention](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-11) 







 Next steps 



* [Operational logging](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-operational)
Audit and Accountability (AU) [AU-3 Content of Audit Records](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-3) <br>[AU-4 Audit Log Storage Capacity](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-4) <br>[AU-5 Response to Audit Processing Failures](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-5) <br>[AU-6 Audit Record Review, Analysis. and Reporting](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6) <br>[AU-6 (1) Audit Record Review, Analysis. and Reporting | Automated Process Integration](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-6.1) <br>[AU-7 Audit Record Reduction and Report Generation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-7) <br>[AU-10 Non-repudiation](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-10) <br>[AU-11 Audit Record Retention](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-au-11) 







 Next steps 



* [Audit logging of application provider events and SIEM](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-shared-logging-audit-provider)
Similarly, it is possible for either one organization or multiple organizations to manage the ordering service and contribute nodes.

For more information about the ordering service, see [The Ordering Service](https://hyperledger-fabric.readthedocs.io/en/release-2.2/orderer/ordering_service.html).





 Channels 

A channel is a mechanism that provides a private layer of communication, allowing subsets of network members to create a separate ledger for their transactions. Channels are not just private in the sense that network members who are not a part of the channel are unable see the transactions, they are also secret in the sense that unless a network member is a part of the channel, they will not even know that the channel exists.

Multiple channels can be created between members, thus supporting one of the [many mechanisms to implement privacy](https://developer.ibm.com/tutorials/cl-blockchain-private-confidential-transactions-hyperledger-fabric-zero-knowledge-proof/). As discussed in the section on [peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-component-overviewblockchain-component-overview-peer), data in a blockchain network is stored on peers in a ledger. Each channel has a separate ledger that holds the transactions (which include configuration transactions) for that channel.

The IBM Blockchain Platform allows channels to be easily created and managed. Channel configuration updates allow the members of a channel to edit channel parameters to fit their use case. For example, more members can be added to a channel, or the capabilities of a channel can be changed. Because changes to a channel must be approved by channel members, the IBM Blockchain Platform provides a mechanism for the collection of necessary signatures.

For more information about channels and how to use them, see the [Hyperledger Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-2.2/channels.html).





 Smart contracts 

Before businesses can transact with each other, a common understanding about rules and processes must be reached and defined.