vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Deprecation lifecycle of Terraform releases 

It is good to always upgrade to the current Terraform release supported by Schematics. For compliance and security considerations, remain on a Terraform release with HashiCorp Configuration Language (HCL) provided maintenance and security fixes. For more information about Terraform fix support, Schematics end of marketing dates for Terraform releases, and end of support, see the [deprecation schedule](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-versiondeprecate-timeline).

For more information about updating the in use Terraform release, see [Upgrading the Terraform workspace version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionmigrate-steps12). Terraform v1.0 was a major release for Terraform, marking the transition to a stable 1.x release. HCL made [compatibility promises for the 1.x releases](https://developer.hashicorp.com/terraform/language/v1-compatibility-promises), that for core Terraform features and function, no changes are needed to HCL templates to upgrade through the 1.x releases.



 Schematics Terraform depreciation lifecycle 

The table outlines the timetable of support that is provided by Schematics for Terraform releases. For more information about the maintenance and fixes, see the following sections.



Depreciation lifecycle

 Timescale Schematics <br>operations Terraform Maintenance and security fixes Upgrade 

 0-6 months Full operations Yes Suggested 
 6-12 months Full operations No Suggested. Upgrade if Terraform fix needed. 
 12 - 24 months Workspace creation restricted No Suggested. Upgrade if Terraform fix needed. 
 24 months Workspace execution restricted No Needed 





 Terraform maintenance and fixes 

Schematics supports Terraform releases in line with [Terraform support and end-of-life policy](https://support.hashicorp.com/hc/en-us/articles/360021185113-Support-Period-and-End-of-Life-EOL-Policy).
curl -X POST "$vpc_api_endpoint/v1/images?version=2021-05-20"
$iam_token" -d
{
"name": "test-ifv-boot-volume",
"source_volume": {
"id": "4fec84ef-baf9-405d-bf3b-9d5a60e068f7"
}
}
<-- </section "id="section-ifv-create-image-boot-id" "> --><-- </section "id="section-ifv-vpc-api-list-instance" "> --><-- <section "id="section-ifv-import-schedule-ilm-status-change-API" "> --> Scheduling custom image lifecycle status changes by using the API When you create an image from volume by using the application programming interface (API), you can schedule the lifecycle status changes of the IBM Cloud VPC image from volume at the same time.The name can't be used by another image in the region and names that start with ibm- are reserved for system-provided images. Specify the source.volume subproperty to indicate the source of the image from volume.To schedule the deprecation_at or obsolescence_at properties, specify a date in the ISO 8601 (YYYY-MM-DDThh:mm:ss+hh:mm) date and time format.<-- <ul> --> * YYYY is the four digit year * MM is the two digit month * DD is the two digit day * T separates the date and time information * hh is the two digit hours * mm is the two digit minutes * +hh:mm or -hh:mm is the UTC time zone<-- </ul> -->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:00When scheduling the date and time, you can't use your current date and time.
* UI
* CLI
* API







 Updating context-based restrictions 

You can update context rules at any time by providing a new description, which helps identifying the purpose of the rule, or selecting a new list of resources and network environments.

To update a context-based restrictions rule, you must be assigned the administrator role on the account management service.



 Updating rules 

To edit the context-based restrictions on your cloud resources, complete the following steps.



1. In the IBM Cloud console, click Manage > Context-based restrictions, and select Rules.
2. Select the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) on the rule you want to update, and select Edit.
3. To update the scope of APIs whose operations are restricted by your rule, select All APIs or Specific APIs. Then, click Apply or Continue.
4. To update the scope of resources for the restriction, you can select All resources or Specific resources based on the available attributes, such as resource group or location. Then, click Apply or Continue.
5. Click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg) in the summary panel to update an existing context.



1. Update the allowed endpoint types.



* Set the toggle to No to allow all service supported endpoint types.
* Set the toggle to Yes to allow only specific endpoint types.



2. Update the nework zones. You can select new network zones or deselect network zones to remove them.



6. Then, click Apply.
7. Click the Remove icon !
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/openshift?topic=openshift-userschecking-perms).



1. Log in to the [Red Hat OpenShift on IBM Cloud 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/openshift?topic=openshift-reservationsri-about-billing).
For more information about available command options, see [file duplicate-convert-status](https://softlayer-python.readthedocs.io/en/latest/cli/file/file-duplicate-convert-status).





 Updating data on the duplicate from the parent volume with the API 

As time passes and the primary volume changes, the duplicate volume can be updated with these changes to reflect the current state through the refresh action. The refresh involves taking a snapshot of the primary volume and then, updating the duplicate volume by using the data from that snapshot.

A refresh incurs no downtime on the primary volume. However, during the refresh transaction, the duplicate volume is disabled and must be remounted after the refresh is completed.

The refresh process can be time-consuming. You might find that you have new data that you want to add to the duplicate before the running refresh is finished. If that's the case, you can make a second call to refreshDuplicate and specify the second, forceRefresh parameter as true to stop all ongoing and pending refresh transactions, and initiate a new refresh. If the second parameter is set to false or it is not specified, the call fails if another refresh is already in progress.

The force refresh process works only on independent volumes.



 REST API example 



* URL - https://USERNAME:APIKEY@api.softlayer.com/rest/v3.1/SoftLayer_Network_Storage/duplicateVolumeId/refreshDuplicate
* Type - POST
* Request body -

{
"parameters": [primaryVolumeSnapshotId, true OR false]
}







 SOAP API example 



* URL - https://api.softlayer.com/soap/v3.1/SoftLayer_Network_Storage
* Type - POST
* Request body -

<?xml version="1.0" encoding="UTF-8"?>
It might be regularly disconnected by the server for any number of reasons, which include maintenance, security, or network errors. Code that uses the changes feed must be designed to use a recently saved sequence ID as a since value to make a new request to resume the changes feed after an error or disconnection.





If the use case is based on the following statement, then this result cannot be achieved with the IBM Cloudant changes feed.

"Fetch me every document that has changed since a known date, in the order they were written."

The IBM Cloudant database does not record the time as each document change was written. The changes feed makes no guarantees on the ordering of the changes in the feed - they are not guaranteed to be in the order they were sent to the database.

However, you can achieve this use case by storing the date of change in the document body:

{
"_id": "2657",
"type": "order",
"customer": "bob@aol.com",
"order_date": "2022-01-05T10:40:00",
"status": "dispatched",
"last_edit_date": "2022-01-14T19:17:20"
}

And you can create a MapReduce view with last_edit_date as the key:

function(doc) {
emit(doc.last_edit_date, null)
}

This view can be queried to return any documents that are modified on or after a supplied date and time:

/orders/_design/query/_view/by_last_edit?startkey="2022-01-13T00:00:00"

This technique produces a time-ordered set of results with no repeated values in a performant and repeatable fashion. The consumer of this data does not need to manage the data idempotently, making for a simpler development process.





The IBM Cloudant changes feed is good for the following tasks:



* Powering IBM Cloudant replication, optionally with a selector to filter some changes.
March 2020 deprecation notice
: To help us continue to improve and expand the capabilities of the assistants you build with Watson Assistant, we are deprecating some of the older technologies. Support for the older technologies will end in June 2020. Take action now to test and adopt the new technologies, so your skills and assistants will be ready when the old technologies stop being supported.

The following technologies are being deprecated:



* Legacy version of numeric system entities

We released a whole new infrastructure for our numeric system entities across all languages except Chinese, Korean, Japanese and Arabic. The updated @sys-number, @sys-date, @sys-time, @sys-currency, and @sys-percentage entities provide superior number recognition with higher precision. For more information about the new system entities, see [System entity details](https://cloud.ibm.com/docs/assistant?topic=assistant-system-entities).

The old version of the numeric system entities will stop being supported in June 2020 for English, Brazilian Portuguese, Czech, Dutch, French, German, Italian, and Spanish dialog skills.

Action: In each dialog skill where you use numeric system entities, go to the Options>System entities page and turn on the new system entities. Take some time to test the new version of system entities with your own dialogs to make sure they continue to work as expected. As you adopt the new system entities, share your feedback about your experience with the new technology.
* Person and location system entities

The @sys-person and @sys-location system entities, which were available in English as a beta only, are being deprecated. Consider using contextual entities as a way to capture these types of proper nouns. Instead of trying to add a dictionary-based entity that covers every permutation of the names for people or cities, for example, you can teach your skill to recognize the context in which such names are used. For more information about contextual entities, see [Annotation-based method](https://cloud.ibm.com/docs/assistant?topic=assistant-entitiesentities-annotations-overview).
Maintenance 



  2023 Maintenance Windows 

Maintenance Windows generally apply to production environments only.

Standard maintenance windows for Production environments are planned twice monthly on weekends (Saturday / Sunday). Non-Production environment maintenance is performed on weekdays.

The IBM SRE team may choose to use all, some, or none of the planned maintenance windows and will proactively notify customers 5 days prior to any Non-Production outage and 10 days prior to any Production outage via the [Client Communications Center (CCC)](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-client-communications-center).

Systems are not available to users during maintenance windows.

Change Freeze period for year end 2023 is December 16, 2023 through January 2, 2024 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 Maximo Application Suite SaaS SRE team also does not schedule any maintenance during the change freeze period.





  Upgrade Policy 

Application and MAS component Upgrades are on a defined schedule based on the Maximo 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 IBM Maximo Application Suite SaaS SRE team may need to schedule unplanned emergency maintenance outages outside of a Planned Maintenance window. The IBM Maximo Application Suite SaaS SRE 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 not available. There are no exceptions.
* [Supercede a product](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_superseding_a_product.html)







 Changing product availability 

Restrict a product to specific consumers or endpoints, or remove a product from the developer portal.



* [Approve product requests](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_accessrequests_product.html)
* [Update gateway services](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/tapic_product_update_gw.html)
* [Set a product's visibility](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_change_product_availability.html)
* [Deprecate a product](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_deprecate_product.html)
* [Retire a product](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_retire_product.html)
* [Remove a product](https://www.ibm.com/support/knowledgecenter/SSMNED_v10cloud/com.ibm.apic.apionprem.doc/task_unpublish_product.html)
+ resource_plan_id = (known after apply)
+ resource_status = (known after apply)
+ restored_at = (known after apply)
+ restored_by = (known after apply)
+ scheduled_reclaim_at = (known after apply)
+ scheduled_reclaim_by = (known after apply)
+ service = "event-notifications"
+ service_endpoints = (known after apply)
+ state = (known after apply)
+ status = (known after apply)
+ sub_type = (known after apply)
+ tags = (known after apply)
+ target_crn = (known after apply)
+ type = (known after apply)
+ update_at = (known after apply)
+ update_by = (known after apply)
}

Plan: 4 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.

Enter a value: yes

ibm_resource_instance.terraform_demo: Creating...
ibm_resource_instance.terraform_demo: Still creating... [10s elapsed]
ibm_resource_instance.terraform_demo: Still creating... [20s elapsed]
ibm_resource_instance.terraform_demo: Still creating... [30s elapsed]
ibm_resource_instance.terraform_demo: Still creating... [40s elapsed]
ibm_resource_instance.terraform_demo: Still creating... [50s elapsed]
ibm_resource_instance.terraform_demo: Creation complete after 52s [id=crn:v1:bluemix:public:event-notifications:us-south:a/4a74f2c31f554afc88156b73a1d577c6:24547d88-e455-548f-cb6e-ge921g6d3025::]
The following patterns represent the allowed condition permutations:



Table 1. Allowed condition patterns for time-based conditions.

 Pattern Example 

 time-based-conditions:once Temporary access on a specific day from 9 AM to 5 PM UTC-5. 
 time-based-conditions:weekly:all-day Recurring access Mon-Fri UTC-5 all day. 
 time-based-conditions:weekly:custom-hours Recurring access Mon-Fri 9 AM to 5 PM UTC-5. 



IAM prevents combining one-time temporary conditions with weekly recurring conditions in the same policy definition.





 Before you begin 

Make sure that you have the latest version of the IBM Cloud CLI so that you can use conditions in your access policies.

To determine your IBM Cloud CLI version, run the following command:

ibmcloud -v

You must use the latest version of the CLI. If you aren't using the latest version, run the following command to update your CLI:

ibmcloud update

If you are running the current release, the following output is displayed:

Checking for updates...
No update required. Your CLI is already up-to-date.

For more information, see [Installing the stand-alone IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli).





 Before you begin 

Make sure that you call the v2/policies URI, which is https://iam.coud.ibm.com/v2/policies, so that you can use conditions in your access policies. For more information, see the [IAM Policy Management API](https://cloud.ibm.com/apidocs/iam-policy-management) and [change log](https://cloud.ibm.com/docs/account?topic=account-api-change-log).





 Creating a temporary time-based condition 

You can assign access for a finite duration by specifying a date and time range that determines when the condition grants and terminates access.
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 2m21s
Created: 2021-03-14T13:37:51-05:00

Destination Type: app
Destination: myapp
Schedule: 0 0 * * 
Time Zone: UTC
Ready: true

Events:
Type Reason Age Source Messages
Normal FinalizerUpdate 12s pingsource-controller Updated "mycronevent" finalizers

From this output, you can see that the destination application is myapp, the schedule is 0 0 * * * (every day at midnight), and the Ready state is true.





 Updating your cron subscription with the CLI 

To update the cron subscription with the CLI, use the [ibmcloud ce subscription cron update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-update) command. For example, update the mycronevent subscription to change the schedule to sends an event to an app called myapp every 2 minutes.

ibmcloud ce sub cron update --name mycronevent --schedule '/2 * * * '

To verify that your cron subscription was successfully updated, run the ibmcloud ce sub cron get --name mycronevent command. The schedule for the subscription is updated.

Example output

Getting cron source 'mycronevent'...
OK

Name: mycronevent
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 2m21s
Created: 2021-08-31T16:00:49-04:00

Destination Type: app
Destination: myapp
Schedule: /2 * * *
To understand the billing impact of upgrading a Pre-production destination to Production destination, see [here](https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-destinations-pushen-destinations-push-charge-preprod-to-prod).

To modify the destination,



* Select the pre-production destination from the list of destinations
* Click the three vertical dots in the selected pre-production destination to access the overflow menu
* Click Edit, which brings the editable view of the selected destination.
* Click the Production destination tile to change the destination.
* Click Add.



You cannot change a Production destination to Pre-production destination.
* Ensure that the date requested is not in the past.
* Check whether a requested reservation time falls within the seating time window.
* Confirm the user's input.
* Ensure that the number of guests provided is larger than zero.
* Indicate that you are replacing one value with another.



To validate user input, complete the following steps:



1. 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-date slot.
2. From the Options![More icon](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) menu in the Configure slot 1 header, select Enable conditional responses.
3. 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.
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.