vania-janet/multiturn-rag-retrieval-data huggingface dataset:
The process for updating a credit card requires a manual review that might take a few days to process. To view your open change request cases, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).

You might manage your payment method on a separate billing platform. You can easily register, update, or delete a payment method by going to [IBM Billing](https://myibm.ibm.com/billing/).

For more information about how to manage your payments, see [Managing your payment method](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-linkedusageprereqs-payments).





 Tracking your usage 

To view usage data for resources, you must be assigned the correct access. Access can be assigned at the account level or to individual resource groups and Cloud Foundry orgs.



* To view usage for all resources in the account, you need an access policy with the Administrator role on the Billing account management service.
* To view usage only for specific IBM Cloud Identity and Access Management (IAM) resources, you need the Viewer role or higher on the resource group.
* To view usage for only specific Cloud Foundry services, the Billing manager role must be applied at the org level. Billing managers can see the details for only the organizations in which they are assigned the Billing manager role.



You can limit the access to view the usage for a specific resource group by assigning the viewer role or higher on all Identity and Access enabled services within that resource group.





 Managing your invoices 

If you have a Pay-As-You-Go account that's billed in US dollars, you can view your invoice in the IBM Cloud console by going to Manage > Billing and usage, > and clicking Invoices.

If you own one of the following accounts, you can view your invoice on the [IBM Invoices](http://ibm.com/invoices) website, which is linked from the [Invoices page](https://cloud.ibm.com/billing/invoices) in the console.
The following table describes important dates that you need to be aware of if you have services that run in the data centers that are set to close. You receive notifications if you have services in the data centers that are closing.



Table 2. Timeline for data center migration

 Date Data Center Migration Milestone 

 03 April 2023 Official announcement for all impacted customers in the following data centers: DAL05, SJC01, and WDC01 
 03 April 2023 Stop provisioning for new customers in the following data centers: DAL05, SJC01, and WDC01 
 14 August 2023 Exisiting customers of DAL05, SJC01, and WDC01 will not be able to place new orders. 
 23 January 2024 Network maintenance Dallas (DAL05): 10:00 AM US Eastern Time (14:00 GMT). 
 24 January 2024 Network maintenance San Jose (SJC01): 10:00 AM US Eastern Time (14:00 GMT). 
 25 January 2024 Network maintenance Washington DC (WDC01): 10:00 AM US Eastern Time (14:00 GMT). 
 03 April 2024 Last date to migrate data before consolidation of DAL05, SJC01, WDC01 begins 
 04 April 2024 Consolidation of DAL05, SJC01 and WDC01 begins
"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:52:52Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"enabled": false,
"interval_month": 3
}
}
---------------------------------------------------------------------------------------------------------------------------------------------------





 Required parameters 



* KEY_ID_OR_ALIAS

The v4 UUID or alias of the key that you want to query. To retrieve a list of your available keys, run the [kp keys](https://cloud.ibm.com/docs/key-protect?topic=key-protect-key-protect-cli-referencekp-keys) command.







 Optional parameters 



* -m, --monthly-interval

Set the key rotation interval in months. The rotation interval must be 1 to 12 months.
* -e, --enable or -d, --disable

By default, key rotation policy is enabled.
Change compatibility 

API changes must be assessed and designed to consider compatibility. The backward-compatibility of each change MUST be determined by using the directives in the [determining compatibility](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-change-compatibilitydetermining-compatibility) section.

Backward-compatible changes SHOULD be made as evolutionary updates and backward-incompatible changes SHOULD be made as versioned updates. Rarely, backward-incompatible changes MAY be made as breaking updates.



 Kinds of updates 



 Evolutionary updates 

Evolutionary updates incorporate backward-compatible changes into an existing major version of an API and (if applicable) across all version dates. Client applications need not use a new major version or new version date to employ features made available in such updates.

If feasible without significant compromise to the usability, consistency, or robustness of the API, a change SHOULD be designed for backward-compatibility and made as an evolutionary update.





 Versioned updates 

Versioned updates incorporate backward-incompatible changes into a new major version or a new version date. Versioned updates require client applications to specify the new version to use features made available in the changes, and protect unchanged clients from being impacted by the updates.

If a change cannot be made backward-compatible, or if backward-incompatibility is necessary to maintain the usability, security, or robustness of the API, the change SHOULD be made as a versioned update.





 Breaking updates 

In rare cases, it might be necessary to make a backward-incompatible change retroactive for a major version and (if applicable) across all version dates. Such changes are considered "breaking," because they could affect existing clients that are using existing API versions.

Breaking API changes that are needed to mitigate a vulnerability that poses an imminent threat to the security of a service or its users MUST NOT be delayed to accommodate a deprecation period and MUST be coordinated with the organization's broader security incident response team

[1].

Breaking API changes that are needed to adhere to updated security best practices (but not needed to mitigate an imminent threat) MAY be made with an abbreviated deprecation period and SHOULD be preceded by targeted notifications to client maintainers.

Breaking changes MUST be justified by a security issue, legal or regulatory obligation, or undue economic burden.
* IBM will share long-range anticipated upgrade windows upon request via ticket
* Timing is subject to change at IBM’s sole discretion based on software availability & other factors



Non-Production Upgrades



* Clients will be notified via CCC at least 5 business days prior to non-production environment upgrades
* All non-production environments will be upgraded concurrently, without exception
* Non-Production environments are upgraded during weekdays.



Production Upgrades



* Production environments will be upgraded no earlier than 4 weeks after the non-production upgrade
* Some requests (e.g. data back-flow) are unavailable between non-production & Production upgrades
* Clients will be notified via CCC at least 10 business days prior to the Production environment upgrade
* The Production environment will be upgraded on schedule, without exception
* Production environments are upgraded on weekends



Notes:



* Upgrades of both prod or non-prod cannot requested to be done earlier or deferred to later for any reason, such as:
* We have training scheduled on planned maintenance window
* We are in critical stage of implementation phase and env cannot be touched
* We have a golive coming up and system cannot be touched
* We have an executive demo
* Non-prod upgrade broke a business functionality that is critical to the business, so Prod cannot be updated until the bug is fixed
* We need upgrade soon, because the new release has feature we need asap







 Dedicated Cluster Deployment Customers 

Dedicated Cluster Upgrade Policy

The following guidelines apply to MAS-Dedicated (Dedicated Cluster) release schedule:



* MAS-Dedicated comes out on the first Tuesday 30 days after MAS (GA) release.
* For example, MAS 8.10 (GA) will be released by IBM on 3/28/2023 and MAS-Dedicated 8.10 on 5/2/2023
* The release of MAS-Dedicated can be delayed beyond 30 days due to holidays and freeze periods. For example MAS 8.9 was released on 11/22/2022 and MAS Dedicated will be 1/17/2023





Table 1. MAS-Dedicated Release Planning

 Version MAS (GA) Release MAS-Dedicated Release Approx Upgrade Window 

 8.9 11/22/22 1/17/23 March to June
For the first and last months, you are billed a pro-rated amount, according to the dates that the contract is active in the months.

If I don't need reserved worker nodes anymore, can I modify my contract?
: No, you can't modify the terms of the contract, such as the duration, number of worker nodes, or flavor. You can remove any unneeded worker nodes from your clusters, but you can't get a refund for unused capacity in your reservation.







 Creating a reservation 

Create a reservation that you can use to provision worker nodes at a reduced cost by committing to a 1 or 3 year term.

Before you begin, make sure that you have the [Administrator platform access role for the service in IBM Cloud IAM](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms).



1. Log in to the [IBM Cloud Kubernetes Service reservations console](https://cloud.ibm.com/kubernetes/reservations).
2. Click Create reservation.
3. Select the Infrastructure provider to use for your worker nodes.
4. Select the Location for your reservation. Keep in mind that you can't change the location later.



* Geography: The geographic area to filter locations by.
* Availability: Choose single zone or multizone. For multizone areas, you select specific zones for your worker nodes when you create the worker pool.
* Metro: The metro for the location.



5. Configure the Worker nodes for your reservation.



* Click Change flavor to edit the CPU, memory, and other operating systems details of the worker nodes. Keep in mind that you can't change the flavor for the reservation later.
* Enter the Number of worker nodes to create a contract for the initial reservation. You can add contracts for additional worker nodes later.



6. Fill out the Reservation details. For more information about the discounts, see [Billing and discounts](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-about-billing).



* Contract length: Choose between 1 or 3 years for the initial contract duration.
"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:52:52Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"enabled": false,
"interval_month": 3
}
}
---------------------------------------------------------------------------------------------------------------------------------------------------





 Required parameters 



* KEY_ID_OR_ALIAS

The v4 UUID or alias of the key that you want to query. To retrieve a list of your available keys, run the [kp keys](https://cloud.ibm.com/docs/key-protect-cli-pluginkp-keys) command.







 Optional parameters 



* -m, --monthly-interval

Set the key rotation interval in months. The rotation interval must be 1 to 12 months.
* -e, --enable or -d, --disable

By default, key rotation policy is enabled.
"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:52:52Z",
"updatedBy": "user id ...<redacted>...",
"rotation": {
"enabled": false,
"interval_month": 3
}
}
---------------------------------------------------------------------------------------------------------------------------------------------------





 Required parameters 



* KEY_ID_OR_ALIAS

The v4 UUID or alias of the key that you want to query. 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 



* -m, --monthly-interval

Set the key rotation interval in months. The rotation interval must be 1 to 12 months.
* -e, --enable or -d, --disable

By default, key rotation policy is enabled.
Run the [ibmcloud resource service-instance-update](https://cloud.ibm.com/docs/cli?topic=cli-ibmcloud_commands_resourceibmcloud_resource_service_instance_update) command:

ibmcloud resource service-instance-update NAME --service-plan-id RESOURCE_PLAN_ID

Where



* NAME is the name of the instance
* service-plan-id indicates the type of plan.
* RESOURCE_PLAN_ID is the ID of the plan that you want to set. To get the service plan IDs, see [Service plans](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-service_plan).



For example, to change the service plan of an instance to the 7 days retention plan, run the following command:

ibmcloud resource service-instance-update logdna-instance-01 9aae7491-5cb6-43eb-9b7a-3e0456c781f0
Release notes for Language Translator 

IBM is announcing the deprecation of the IBM Watson® Language Translator service for IBM Cloud® in all regions. As of 10 June 2023, the Language Translator tile will be removed from the IBM Cloud Platform for new customers; only existing customers will be able to access the product. As of 10 June 2024, the service will reach its End of Support date. As of 10 December 2024, the service will be withdrawn entirely and will no longer be available to any customers.

The following new features and changes to the service are available.



 Service API Versioning 

API requests in Language Translator v3 require a version parameter that takes a date in the format version=YYYY-MM-DD. Whenever we change the API in a backwards-incompatible way, we release a new minor version of the API.

Send the version parameter with every API request. The service uses the API version for the date you specify, or the most recent version before that date. Don't default to the current date. Instead, specify a date that matches a version that is compatible with your app, and don't change it until your app is ready for a later version.

The current version is 2018-05-01.





 13 January 2023 

Cloud Foundry deprecation and migration to resource groups
: IBM announced the deprecation of IBM Cloud Foundry on 31 May 2022. As of 30 November 2022, new IBM Cloud Foundry applications cannot be created and only existing users are able to deploy applications. IBM Cloud Foundry reaches end of support on 1 June 2023. At that time, any IBM Cloud Foundry application runtime instances running IBM Cloud Foundry applications will be permanently disabled, deprovisioned, and deleted. For more information about the deprecation, see [Deprecation of IBM Cloud Foundry](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-deprecation).

To continue to use your IBM Cloud applications beyond 1 June 2023, you must migrate to resource groups before that date. Resource groups are conceptually similar to Cloud Foundry spaces.
"priority": 100,
"paused": false,
"description": "do not challenge login from office"
}
-s, --json-str: Deprecated. The JSON data describing a firewall-rule.-j, --json-file: Deprecated. A file contains input JSON data.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-a-firewall-rule-options" "> --><-- <section "id="section-update-a-firewall-rule-examples" "> --> Examples Update firewall-rule 372e67954025e0ba6aaa6d586b9e0b60. ibmcloud cis firewall-rule-update 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b60 --expression "ip.src eq 93.184.216.1 and http.request.uri.path "^./wp-login.php$"" --action allow --priority 200 --paused off --description "do not challenge login from office" -i "cis-demo"

ibmcloud cis firewall-rule-update 31984fea73a15b45779fa0df4ef62f9b 372e67954025e0ba6aaa6d586b9e0b60 --json '{"expression": "ip.src eq 93.184.216.1 and http.request.uri.path "^./wp-login.php$"", "action": "allow", "priority": 100, "paused": false, "description": "do not challenge login from office"}' -i "cis-demo"
[Edit response](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/edit-slot.png) icon for the @sys-date slot.
2. From the More![More icon](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) menu, select Open JSON editor, and then edit the JSON that defines the context variable. Add a method that reformats the date so that it converts the 2017-12-29 value into a full day of the week, followed by the full month and day. Edit the JSON as follows:

{
"context": {
"date": "<? @sys-date.reformatDateTime('EEEE, MMMM d') ?>"
}
}

The EEEE indicates that you want to spell out the day of the week. If you use 3 Es (EEE), the day of the week will be shortened to Fri instead of Friday, for example. The MMMM indicates that you want to spell out the month. Again, if you use only 3 Ms (MMM), the month is shortened to Dec instead of December.
3. Click Save.
4. To change the format in which the time value is stored in the $time context variable to use the hour, minutes and indicate AM or PM, click the Edit response![Edit response](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/edit-slot.png) icon for the @sys-time slot.
5. From the More!
You can use this information for planning purposes, such as to estimate the general time that the version might become unsupported.

Dates that are marked with a dagger (†) are tentative and subject to change.



Release history for Red Hat OpenShift on IBM Cloud version 4.10.

 Supported? Red Hat OpenShift / Kubernetes version Release date Unsupported date 

 Deprecated 4.10 / 1.23 27 April 2022 29 November 2023† 







 Preparing to update 

If you want to upgrade a 4.9 cluster with RHEL 7 worker nodes to 4.10, [replace your RHEL 7 worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_versions_410410_rhel-migrate) with RHEL 8 worker nodes before you follow the steps to upgrade to version 4.10.

Gateway-enabled clusters
: Classic clusters created with the --gateway-enabled option do not support RHEL 8 worker nodes, and therefore are not supported for version 4.10. You cannot update your cluster to version 4.10 if it has the gateway-enabled cluster controller installed.



 Update before master 

The following table shows the actions that you must take before you [update the cluster master](https://cloud.ibm.com/docs/openshift?topic=openshift-updatemaster).



Changes to make before you update the master to Red Hat OpenShift 4.10

 Type Description 

 Unsupported: Deprecated and removed Red Hat OpenShift features For more information, review the [Red Hat OpenShift version 4.10 deprecated and removed features](https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.htmlocp-4-10-deprecated-removed-features). 
 Kubernetes API server metrics job name changed Kubernetes API server metrics now use job kube-apiserver rather than cluster-version-operator. Update any custom metrics and alerts to use the new job name.
If you need to set specific rate limits for specific operations, you must set them within the operations themselves and this setting overrides the setting at the Plan level.

IBM API Connect also supports the implementation of multiple versions of Products. You can choose version numbers and use them to aid the development of your Products and Plans.

Note: The version for a Product is distinct from the version of any APIs that are contained in the associated Plans. Plans cannot themselves have their own version, they use the version of their parent Product.

For more information about the tasks that are required to manage APIs, see [Managing APIs](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-managing_apis).





 Catalogs 

Products must be staged to a Catalog and then published to Developer organizations to become available to application developers. In API Connect, you can create multiple Catalogs. Catalogs are useful for separating Products and APIs for testing before you make them available to Developer organizations.

A Catalog is a staging target, and behaves as a logical partition of the gateway and the Developer Portal. The URL for API calls and the Developer Portal are specific to a particular Catalog. In a typical configuration, an API provider organization uses a development Catalog for testing APIs under development and a production Catalog for hosting APIs that are ready for full use. A common approach is to have a development cloud with a development Catalog, a few test Catalogs and a production cloud that might have its own test Catalog.



 Catalog settings 

You can apply the following settings to a Catalog:



* Development: By default, a development Catalog is provided for you. A development Catalog must be used only for test purposes. In a development Catalog, staging and publishing actions are forced. If you republish a Product, the new version overwrites the old version without warning. If conflicts are found, they are automatically resolved by the system. Unpublish actions happen automatically. When you use the test tool in a development Catalog, any Product that you test overwrites staged and published Products. The newer version replaces the old version even if the operations are being used on the Developer Portal.
When collection processing completes, you receive a status message that states, Your documents have finished processing! You can now work with your full data set..
* The Next sync scheduled for date and time. Your current crawl schedule settings determine the Next sync scheduled for, which updates if you change your crawl schedule in the Sync settings tab. Also, when your next scheduled crawl begins, the Next sync scheduled for automatically updates.
* A list of warnings and errors
* Any fields that the crawler identified from your data
* Any enrichments that were added to your data and the option to Add enrichments
* Available sample queries and the option to Build your own query



Errors and warnings tab:



* A list of any warnings and errors that might appear while your collection processes, such as the affected file name and its associated document ID



Sync settings tab:



* The option to change your security credentials. If your security credentials for connecting to a data source change, you must update your credentials. To update your credentials, in the Your service's credentials pane, click Edit credentials.
* The option to edit the content that you want to crawl in the Enter the data that you would like to sync pane. You can change or delete any URL or file path that you already specified. To delete a URL or file path, click the minus icon next to the ![Settings](https://cloud.ibm.com/docs-content/v1/content/ded4adc3ea0bd2a81b113c579f2b1183926da211/discovery/images/icon_settings.png) icon.
* The option to change your crawler schedule in the Additional settings pane by clicking Sync frequency
* The Crawl settings dialog box. For example, if you select Web Crawl and you already added a start URL, you can click the !