vania-janet/multiturn-rag-retrieval-data huggingface dataset:
An action that uses a disabled runtime can still be read and deleted.

Migrate actions that are running on a deprecated or disabled runtime to a different runtime version by updating it. To update the runtime, see [changing action runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_update).

These runtimes (kinds) are deprecated:



* go:1.17 (deprecated)
* nodejs:12 (deprecated)
* nodejs:10 (deprecated)
* php:7.4 (deprecated)
* python:3.7 (deprecated)
* python:3.9 (deprecated)
* dotnet:2.2 (deprecated)
* ruby:2.6 (deprecated)



These runtimes (kinds) are disabled:



* ballerina:0.990 (disabled)
* go:1.11 (disabled)
* go:1.15 (disabled)
* nodejs (disabled)
* nodejs:6 (disabled)
* nodejs:8 (disabled)
* php:7.1 (disabled)
* php:7.2 (disabled)
* php:7.3 (disabled)
* python (disabled)
* python:2 (disabled)
* python:3.6 (disabled)
* ruby:2.5 (disabled)
* swift (disabled)
* swift:3 (disabled)
* swift:3.1.1 (disabled)
* swift:4.1 (disabled)
* swift:4.2 (disabled)



For more information about supported and disabled runtimes, see [Available images and runtimes per region](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesruntimes_per_region).





 JavaScript runtimes 

By default, all Node.js actions are executed in a version 16 environment.
`@sys-date.before(now())` You cannot make a reservation for a day in the past. Clear slot and prompt again 



5. Add a second conditional response that is displayed if the user provides a valid date. This type of simple confirmation lets the user know that her response was understood.



Slot 1 conditional response 2 details

 Condition Response Action 

 `true` $date it is Move on 



6. From the edit view of the node with slots, click the Edit slot![Edit slot](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/edit-slot.png) icon for the @sys-time slot.
7. From the Options![More icon](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) menu in the Configure slot 2 header, select Enable conditional responses.
8. In the Found section, add a conditional response by clicking the Edit response![Edit response](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/edit-slot.png) icon.
9. Add the following conditions and responses to check whether the time that the user specifies falls within the allowed time window:



Slot 2 conditional response details

 Condition Response Action 

 `@sys-time.after('21:00:00')` Our last seating is at 9 PM. Clear slot and prompt again 
 `@sys-time.before('09:00:00')` Our first seating is at 9 AM. Clear slot and prompt again 



10.
A non-deprecated major version of a service MUST support up to (but not beyond) the current date (from 00:00 UTC of that date).

From an API client developer's perspective, any date in the supported range is equally valid. From a service developer's point of view, version dates provided by the client SHOULD be canonicalized to a small number of "inflection" dates — version dates at which the behavior of the service actually changes. This could be considered an exception to the general policy to avoid [unnecessary input canonicalization](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-robustnessinput-canonicalization).

When a client provides a version date between two inflection dates (or after the most recent inflection date), the behavior of the API MUST match the behavior defined for the closest prior inflection date. For example, if the behavior of an API mostly recently changed for the 2021-06-01 version date and a client provides 2021-06-30, that service MUST behave as if 2021-06-01 was provided.

An update to the service MAY move the oldest supported API version date forward in accordance with deprecation policies. A deprecated major version SHOULD establish a fixed last supported date when its deprecation is announced.





 Version dates 

An update to a service MAY support new API behavior specific to a new API version date, or across version dates, depending on the [compatibility](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-change-compatibility) of the change. The service implementation supporting a change specific to a new API version date (e.g., 2019-11-19) MUST be released prior to that date.





 Client developer directives 

Client developers SHOULD be encouraged to use the current date as a version date during development and MUST be encouraged to use a fixed value for testing and production release.
--outage-duration duration of the outage (format: 'd HH:mm:ss' or 'none')
--priority change priority, valid options: critical, high, moderate, low, planning (defaults to value found in the pull request)
--environment the environment for the deployment
--purpose purpose explanation (default to value found in the pull request)
--description description of the change
--backout-plan description of the backout plan (defaults to the value found in the PR)
--planned-start planned start time of the change (required format: YYYY-MM-DD HH:mm:ss, e.g 2020-05-13 13:00:12, in UTC)
--planned-end planned end time of the change (required format: YYYY-MM-DD HH:mm:ss, e.g 2020-05-13 13:00:12, in UTC)
--deployment-ready readiness for deployment (choices: 'yes', 'no', default: 'yes')
--type change request type, option: standard, emergency
--provider (Optional) Change Management service provider (choices: 'servicenow', 'servicenow-v3', default: 'servicenow')



* Provide a file name to parse the change request data from. JSON format is expected.



Options:

--file --f json file name to parse the cr data from
--provider (Optional) Change Management service provider (choices: 'servicenow', 'servicenow-v3', default: 'servicenow')

Example file:

{
"type": "emergency",
"assignedto": "alexandra.szanto@ibm.com",
"backoutplan": "rollback",
"priority": "critical",
"purpose": "bugfix",
"description": "test description",
"environment": "crn:v1:bluemix:public::ch-ctu-2::::",
"impact": "bug",
cocoa change-request task list "<insert-change-request-id-here>"





 cocoa change-request task update 

This command is deprecated and will be removed in 2.0.0. Use cocoa change-request attachment update instead!

Updates a Change Task in a specific Change Request.

Options:

--change-request-id The change request the change task belongs to [string] [required]
--change-task-id The change task id to be updated [string] [required]
--description A more detailed description for the Change Task. [string]
--data Data for the Change Task or a path prefixed with @ to read the data from. [string]
--provider (Optional) Change Management service provider (choices: 'servicenow', 'servicenow-v3', default: 'servicenow')

Required Environment Variables, if you are using ServiceNow v1 or v2 provider:

SERVICENOW_TOKEN= ServiceNow API Token
SERVICENOW_URL= ServiceNow API URL

Required Environment Variables, if you are using ServiceNow v3 provider:

IAM_ACCESS_TOKEN= Access token obtained from the IAM service corresponding to pnp-ibmcloud-api-key.
SERVICENOW_URL= ServiceNow API URL

Running the command:

$ cocoa change-request task update
--change-request-id='CHGXXXXXXX' --change-task-id='CTASKXXXXXXX' --data='<data-for-the-task>' --description='<description>'

$ cat data.txt | cocoa change-request task update --change-request-id='CHGXXXXXXX' --change-task-id='CTASKXXXXXXX' --data='@/dev/stdin'

$ cocoa change-request task update --change-request-id='CHGXXXXXXX' --change-task-id='CTASKXXXXXXX' --data='@<path/to/file>'





 cocoa change-request attachment add 

Adds a Change attachment to a specific Change Request.
Installed deployments have a More scheduling settings section where you can choose the type of schedule to use to crawl the data source.

The choices for all of the connectors (except the Web crawl connector) are as follows:



* Full crawling: Recrawls the external data source to update documents in the collection.
* Crawling updates (look for new, modified, and deleted contents): Updates the collection only if data in the external data source was added, modified, or deleted since the last crawl.
* Crawling new and modified contents: Updates the collection only if data in the external data source that was added or modified since the last crawl.



Web crawl connector only: The Web crawl connector schedules crawls differently from the other connector types. For the Web crawl connector only, choose among the following options:



* To control the frequency of the crawls yourself, choose this option:

Full crawling

When you choose a full crawl schedule type, the crawl occurs with the frequency that you specify in the Crawl schedule section of the page.
* To allow the system to manage the frequency of the crawls for you, choose one of the following options:

Crawling updates (look for new, modified, and deleted contents) or Crawling new and modified contents

When you choose a schedule type that crawls for updates or for new and modified contents, the frequency that you specify for the crawl schedule is ignored. The frequency with which each document is crawled is variable and is managed entirely by the service. And the frequency changes depending on how often changes are found in a document. For example, if 5 of the 10 documents in a collection changed by the end of the first crawl interval, then the frequency is automatically increased for those 5 documents. Currently, the highest frequency at which these self-managed refreshes can run is daily.

You cannot interrupt the automated management of frequency and you cannot trigger a one-off crawl when these types of scheduled crawls are configured.





If you want to change the flexible crawl schedule settings later, you can go to the Processing settings page, edit the settings, and then click Apply changes and reprocess.

IBM Cloud

The next scheduled crawl is displayed on the Activity page.

If you change the schedule frequency, the next scheduled crawl time might not be what you expect.
: Superseded: This deprecation notice is superseded by the [15 February 2023 service update](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notesspeech-to-text-15february2023). The end of service date for all previous-generation models is now 31 July 2023.

On 15 March 2022, the previous-generation models for all languages other than Arabic and Japanese were deprecated. At that time, the deprecated models were to remain available until 15 September 2022. To allow users more time to migrate to the appropriate next-generation models, the deprecated models will now remain available until 3 March 2023. As with the initial deprecation notice, the Arabic and Japanese previous-generation models are not deprecated. For a complete list of all deprecated models, see the [15 March 2022 service update](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-release-notesspeech-to-text-15march2022).

On 3 March 2023, the deprecated models will be removed from the service and the documentation. If you use any of the deprecated models, you must migrate to the equivalent next-generation model by the 3 March 2023.



* For more information about the next-generation models to which you can migrate from each of the deprecated models, see [Previous-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models)
* For more information about the next-generation models, see [Next-generation languages and models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-ng)
* For more information about migrating from previous-generation to next-generation models, see [Migrating to next-generation models](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-models-migrate).
* On July 12, 2020, the deprecation period for the 2019-06-04 version date ends and the version date is retired.



* API requests that still use the 2019-06-04 version date after July 12, 2020 are automatically changed to use the behavior of the latest version date available. For this example, the latest version available is 2020-05-10.









 Version dates 

The following table shows the service behavior changes for each version date. Switching to a later version date will activate all changes introduced in earlier versions.



 Version date Changes summary Retirement date 

 [2022-08-10](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-aug1022) Language expansion of entities with a new model for improved accuracy and confidence scores.<br><br>Version 2 Russian entity type system.<br><br>Version 2 Swedish entity type system. 
 [2022-04-07](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-apr0722) Bug fix for Version 2 Categories type system. 
 [2020-12-09](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-dec0920) Version 2 English entity type system. 
 [2020-12-02](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-dec0220) Version 2 Korean entity type system.<br><br>Version 2 Spanish entity type system. 
 [2020-08-01](https://cloud.ibm.com/docs/natural-language-understanding?topic=natural-language-understanding-release-notesnatural-language-understanding-aug0120) Taxonomy changes aimed towards standardization of the label names in the default taxonomy.
Deprecated runtimes are only marked as such in the console and in this documentation ([Available images and runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesruntimes_available)).

When you troubleshoot a failing action (400, bad request) to identify whether a disabled runtime is used, check for deprecated=true in the query response. Actions that use a disabled runtime can be only read or deleted. You cannot run such an action.

To update the runtime of this action to a supported one, see [changing action runtime](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_update).
Maintenance Windows 



*  Maintenance Windows generally apply to production environments only.
*  Standard maintenance times are planned twice monthly, in a 6 hour window from 21:00 to 03:00 UTC Saturday / Sunday.
*  The remaining date for planned windows in 2022 is



December 10.



*  The IBM TRIRIGA Application Suite Managed Services team may choose to use all, some, or none of the planned maintenance windows and will proactively notify customers 5-10 days prior to any outage that will be taken.
*  Systems are not available to users during maintenance windows.



Non-Production systems may be scheduled for maintenance during the week, 1- 2 weeks prior to planned maintenance on Production systems to allow additional time for testing.



*  Change Freeze period for year end 2022 is December 17, 2022 through January 2, 2023.



Change Freeze period is in red above. Systems are available to users and all standard automated processes such as database backups continue as normal during the change freeze period. Coordinated changes to environments like application upgrades as an example are not available during this time. The IBM TRIRIGA Application Suite Managed Services team also does not schedule any maintenance during the change freeze period.



  Upgrade Policy: 

Application and TAS component Upgrades are on a defined schedule based on the TRIRIGA Application Suite release schedule and complexity of the upgrade. It is expected customers will be upgraded to the current version within 6 months of release. Upgrades will be deployed first to test and then scheduled for production. The test window length will depend on the size and complexity of the change and will be communicated through the Customer Communications Center as soon as it is available.





  Emergency Maintenance: 

In exceptional cases such as critical security patching, the The IBM TRIRIGA Application Suite Managed Services team may need to schedule unplanned emergency maintenance outages outside of a Planned Maintenance window for Production systems. The IBM TRIRIGA Application Suite Managed Services team will provide as much advanced notice as possible, however depending on criticality of the security patch, 5-10 business days notice may not be possible.





  Exception / Deferral Maintenance Requests: 

All customer environments are managed to several internal and external security and compliance standards. IBM initiated planned maintenance is governed by these standards. For this reason, exceptions or deferral requests are generally not available, but can be evaluated on a case by case basis. To initiate an exception submit a request by opening a case in the [IBM Support Community portal](https://www.ibm.com/mysupport).
[Edit response](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon.
4. Add the following condition and response to check whether the date that the user specifies falls before today:



Slot 1 conditional response 1 details

 Condition Response Action 

 `@sys-date.before(now())` You cannot make a reservation for a day in the past. Clear slot and prompt again 



5. Add a second conditional response that is displayed if the user provides a valid date. This type of simple confirmation lets the user know that her response was understood.



Slot 1 conditional response 2 details

 Condition Response Action 

 `true` $date it is Move on 



6. From the edit view of the node with slots, click the Edit slot![Edit slot](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon for the @sys-time slot.
7. From the Options![More icon](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/kebab.png) menu in the Configure slot 2 header, select Enable conditional responses.
8. In the Found section, add a conditional response by clicking the Edit response![Edit response](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon.
9.
Reminders Ongoing Periodic reminders are sent to all users with running IBM Watson IoT Platform instances that the end-of-support date is coming, with increasing frequency as the date approaches. 
 End-of-Support 1 December 2023 All remaining instances of IBM Watson IoT Platform on IBM Cloud will be permanently disabled and deprovisioned. 







 IBM Watson IoT Platform deprecation details 

Some details of this announcement:



* A deprecation is a process, and we've announced the beginning of that process. It begins with the Announcement via email notice to all users in November 2022 and ends with End-of-Support.
* At the End-of-Support, all IBM Watson IoT Platform instances will, in a short period of time, be stopped and deprovisioned.
* All other services you have been using in IBM Cloud, possibly from your IBM Watson IoT Platform instances, are unaffected. The IBM Watson IoT Platform deprecation refers only to the specific IBM Watson IoT Platform instances that you have running, not services you might use with your IBM Watson IoT Platform instances.
* All IBM Watson IoT Platform paid instances running on IBM Cloud will remain fully functional until the End-of-Support date.
* Reminders of the approaching End-of-Support date will continue to be sent periodically to all users who have IBM Watson IoT Platform instances still running.







 IBM Watson IoT Platform user next steps 

All IBM Watson IoT Platform users need to decide where to move their IoT devices and applications before the IBM Watson IoT Platform End-of-Support date. The following migration options can help you decide which option is right for your organization. There are no plans for a direct replacement for this service.



1. Looking for increased experience and capability? The IBM Watson IoT Platform technology is still available as an embedded component within IBM’s hybrid cloud solutions for Asset and Facilities Management. IBM Maximo Application Suite and IBM TRIRIGA Application Suite are full hybrid cloud solutions for asset management and facilities management, running on Red Hat® OpenShift®.
The content of the workspaces remains accessible and the Terraform release can be updated in Schematics to re-enable operations.

If you choose not to upgrade to the current version of Terraform beyond the restrict workspace execution date:



* Your Schematics workspace data continues to stay in Schematics until you delete these workspaces.
* You cannot do operations on, or destroy the IBM Cloud resources by using Schematics. The resources can still be deleted through the IBM Cloud console or CLI.









 Depreciation Schedule 

You are suggested always to migrate from your in use version of Terraform to the current available version and to remain on Terraform versions with maintenance and security fixes. You can see the current in use version of Terraform in the drop down list of the [Schematics Workspaces](https://cloud.ibm.com/schematics/workspaces/create) configuration page.

Schematics announces the timeline for the deprecation of Terraform versions, the related end of marketing date, and end of support date when you are using the IBM Cloud Schematics service. The month that is provided in the table represents the last day of the Month to restrict workspace creation and execution. The depreciation timeline changes as new Terraform versions are released.



Deprecation timeline as on 27th April, 2023.

 Versions Terraform end of maintenance and security support Phase 1: Restrict workspace creation <br>(End of marketing) Phase 2: Restrict workspace execution <br>(End of support) 

 Terraform v0.x 2021 and earlier May 2022 September 2023 
 Terraform v0.15 July 2021 September 2023 September 2024 
 Terraform v1.0 May 2022 September 2023 September 2024 
 Terraform v1.1 Sept 2022 September 2023 September 2024 
 Terraform v1.2 March 2023 March 2024 March 2025 
 Terraform v1.3 Expected July 2023 Earliest July 2024 Earliest July 2025 
 Terraform v1.4 Expected September 2023 Earliest September 2024 Earliest September 2025 







 User actions 

Follow these steps to upgrade to continue working with the latest versions of Terraform in IBM Cloud Schematics.



1.
Thus, the date of 30 September 2023 at 8:00 p.m. in the North American Central Standard Time Zone (CST) would be 2023-09-30T20:00:00-06:00

When scheduling the date and time, you can't use your current date and time. For example, if it is 8 a.m. on June 12, then the scheduled date and time must be after 8 a.m. on June 12. If you define both the deprecate-at and obsolete-at dates and times, the deprecate-at date must be after the obsolete-at date and time.

ibmcloud is image-create IMAGE_NAME [--source-volume VOLUME_ID] [--deprecate-at YYYY-MM-DDThh:mm:ss+hh:mm] [--obsolete-at YYYY-MM-DDThh:mm:ss+hh:mm]







 Creating an image from a volume by using the API 

Use the regional API to create an image from volume when you create an instance or from an existing instance.



 Before you begin 

Before you can use the API, you must take some preliminary steps. For more information, see [API prerequisites](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentapi-prerequisites-setup).





 Creating an image from volume when you create an instance (API) 

Follow these steps to create an image from volume when you create a new instance. The new instance's boot volume is used for the image, which inherits the encryption from the boot volume. In this scenario, the boot volume uses the default IBM-managed encryption, which is inherited by the new image. You can also specify your own root encryption key in the POST/images call. For more information, see [Create an image from volume and use your root encryption key](https://cloud.ibm.com/docs/vpc?topic=vpc-create-ifvifv-use-crk).

This procedure:



1. Creates an instance and uses its boot volume ID as the source volume.
2.