vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information about Terraform v1.0 availability from HashiCorp Language, see [Terraform v1.0 general availability](https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/1-0).

IBM Cloud Schematics support job queue logs enhancement
: For more information about viewing job queue logs, see [Reviewing the Schematics job details](https://cloud.ibm.com/docs/schematics?topic=schematics-interrupt-jobsch-job-logs).





 11 August 2021 

IBM Cloud Schematics deprecates older version of Terraform
: The end of marketing and end of support of deprecating older version of Terraform provider in IBM Cloud Schematics, see [Deprecating older version of Terraform process in IBM Cloud Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-deprecate-tf-version).







 July 2021 

Review the release notes for July 2021.



 30 July 2021 

IBM Cloud Schematics deprecates Terraform v0.11
: IBM Cloud Schematics deprecates the support of Terraform v0.11 from July 2021. As HashiCorp Configuration Language deprecated Terraform v0.11 in Terraform providers. Terraform v0.15 support
: IBM Cloud Schematics now supports Terraform v0.15 now. You can now select to run your infrastructure code with Terraform version 0.12 or 0.13 or 0.14 or 0.15. Make sure that you use the syntax that is compatible with the Terraform version that you want to use. Note Terraform v0.15 provides you to remote state data sources, cross-compatible between the Terraform v0.14.x and higher version to move between Terraform versions. Also, you can experience a unified console experience across all support platforms, and provides provider-based sensitivity and sensitive functions.
By grouping requests at similar sections of disk, the drive doesn't need to "seek" as often, improving the overall response time for disk operations. On modern Linux implementations, several I/O scheduler options are available. Each of the schedulers has their own unique method of scheduling disk access requests.



* Deadline is the default I/O scheduler on Red Hat 7.9, and usually it does not need to be changed to a different I/O scheduler. It's latency-oriented scheduler and it works by creating a separate read queue and separate a write queue. Each I/O request has a timestamp that is associated with it to be used by the kernel for an expiration time. While this scheduler also attempts to service the queues based on the most efficient ordering possible, the expiration time acts as a "deadline" for each I/O request. When an I/O request reaches its deadline, it is pushed to the highest priority.
* No Operation (NOOP) is a basic scheduler that passes down the I/O that comes to it. This scheduler places all I/O requests into a FIFO (First in, First Out) queue. It's a useful tool for checking whether complex I/O scheduling decisions of other schedulers are causing I/O performance regressions. This scheduler is recommended for setups with devices that do I/O scheduling themselves, such as intelligent storage or in multipathing environments. If you choose a more complicated scheduler on the host, the scheduler of the host and the scheduler of the storage device can compete with each other and decrease performance. The storage device can usually determine best how to schedule I/O. For more information about how to check and configure the I/O scheduler, see Red Hat's [How to use the NOOP or None IO Schedulers](https://access.redhat.com/solutions/109223).
* Completely fair queuing (CFQ) uses both elevators and request merging, and it is a bit more complex than the NOOP or deadline schedulers. It's the standard scheduler for many Linux distributions.
Valid values are: critical, high, moderate, low, no_impact
* Backout Plan Describes the rollback or backout plan.



Along with these fields, you must set two additional fields from the environment properties:



* target-environment-purpose (Required) Valid values are: production, pre_prod. Any non-production deployment would qualify as pre_prod.
* target-environment-detail (Required) A string which describes the target-environment where the change is deployed.



For more information on change request data, see [Data included in change requests](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-cr-data).



 Types of change 

Change Request Management supports two types of change: emergency or regular.

If the current change is an emergency change, add the emergency label to the promotion pull request.







 Step 2: Creating change requests for changes that require planned downtime 

The continuous deployment pipeline automatically approves change requests based on the following conditions:



* Implementing the change does not cause any downtime (outage duration is zero).
* Deployment Readiness is true.



The Change Management automation in the DevSecOps reference implementation assumes that all changes are implemented without planned downtime. If your changes require planned downtime, you must create the change request manually and send it for approval. After it is approved, you can start deployment by providing the change request ID. The pipeline moves ahead to check its approval, and then runs the deployment. For more information, see [Manually approving change requests](https://cloud.ibm.com/docs/devsecops?topic=devsecops-cd-devsecops-approve-cr).

Deployment Readiness is calculated from the evidence that is collected in the continuous integration and continuous deployment stages. If any of the collected evidence suggests a deviation, or an unsuccessful check, scan, or test that is related to the deployed set of artifacts, the Deployment Readiness is set to false, and the Change Request is not auto-approved. The deployment stops, and prevents further steps until the change request is approved.
Self-serve system updates 

Many updates on your Db2 on Cloud Enterprise, Standard, or DR instance are offered as self-serve updates, which means that you have the ability to apply system updates to your instances at a time of your choosing. No email notifications are sent for this type of update. You'll be notified through your console. There might be a time limit within which you must apply the update, typically 30 days, before it is automatically applied to your instance.

However, some updates impact all of the users sharing a common infrastructure, or are required immediately to keep your system secure. You can't schedule these updates. Additional details about these types of updates are coming soon.

The update process can be disruptive, especially for single node instances, so it's advisable to run the update during a maintenance window.

[Enterprise and Standard plan updates](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-self_serve_updatessu_plans)

[DR plan updates](https://cloud.ibm.com/docs/Db2onCloud?topic=Db2onCloud-self_serve_updatessu_dr)



 Enterprise and Standard plan updates 

Enterprise and Standard plans give you the ability to apply system updates to your instances at a time of your choosing.



 Notification 

For self-serve updates, you are notified of an instance system update through the Notifications icon in the upper right of the console.

Zoom

![Update notification](https://cloud.ibm.com/docs-content/v1/content/2a59ee244ed61eb35ab50e45757b42d22f720132/Db2onCloud/images/ss_notification.png)

Figure 1. Self-serve update notification

Clicking View details brings up the System update information window that displays the new Db2 version of Db2 on Cloud.

Zoom

!
1.38.0 21 July 2022 <br><br> * Added support for the --binding-resource-group-id option on the project update command. Use this option to configure service binding access for all service instances in a resource group by specifying the ID of the resource group.<br> * Fixed various bugs.<br><br><br> 
 1.37.0 14 July 2022 <br><br> * Added support for running a Code Engine job indefinitely so that the job does not time out by specifying --mode daemon. Support for daemon mode jobs applies for the following commands: job create, job update, job get, job list, jobrun submit, jobrun resubmit, jobrun get, and jobrun list.<br> * When you specify the --build-source option with the app create, app update, job create, or job update commands, Code Engine now runs a build run without first creating a build. For the apps or jobs that are created with this change, the associated get command output is updated accordingly.<br> * Added the --git-repo-secret-clear option to the build update command. Similarly, added the --build-git-repo-secret-clear option to the app update and job update commands.<br> * Added the --commit-clear option to the build update command. Similarly, added the --build-commit-clear option to the app update and job update commands.<br> * Fixed various bugs.<br> * Updated translations for the CLI.<br> * Upgraded to Go 1.18.4.<br><br><br> 
 1.36.0 23 June 2022 <br><br> * Added support for Kafka event subscriptions. You can now use the subscription kafka commands to create, update, list, delete, and get information about Kafka event subscriptions.<br> * Fixed various bugs.<br><br><br> 
 1.35.0 16 June 2022 <br><br> * Added support for Linux 64 bit ARM for Code Engine CLI.<br> * Fixed various bugs.<br> * Updated translations for the CLI.<br><br><br>
* Priority: (mandatory) One of Critical, High, Moderate, Low, Planning
* Change Request assignee: (mandatory) email-id of the assignee
* Additional Description: Description about the changes in the application
* Purpose: Purpose of the changes that are made to the application
* Explanation of Impact: Impact of the change to the application behavior or environment
* Backout Plan: Steps to back out if the deployment fails



2. Complete the fields in the Pull Request and save.
3. Add the EMERGENCY label to your PR if any compliance checks in CI failed and you want to continue with deployment
4. Merge the Pull Request from the Git Repos and Issue Tracking.



The details of the Pull Request are used by the CD Pipeline to create a Change Request in Change Request Management repository during the CD pipeline run.







 Run the CD pipeline 



 Run Promotion Pipeline 



1. Make sure that CI Pipeline ran successfully before you run the Promotion Pipeline.
2. The Promotion Pipeline creates a Pull Request with the content of the inventory on the Inventory Source Environment (for example: master) branch targeting the Inventory Target Environment branch (for example: staging or prod). An intermediary branch for the PR is created which can be discarded after the PR is merged.



Zoom

![Running the promotion pipeline](https://cloud.ibm.com/docs-content/v1/content/5eb88a2575e30e316dbb83829c7f4c8b1ddbc67c/devsecops/images/run-promotion-pipeline.png)

Figure 28. Running the promotion pipeline



1. After the Promotion Pipeline finishes successfully, the promote task provides you with a link to the previously mentioned Pull Request in the Inventory Repository. The pull request name is in the following format:



promote <Inventory Source Environment> to <Inventory Target Environment>



1. Open the Pull Request in your browser with the link provided in the log. Complete the sections as follows:



* Priority: (mandatory) One of Critical, High, Moderate, Low, Planning
* Change Request assignee: (mandatory) email-id of the assignee
"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.





 What is the IBM Cloudant changes feed good for now? 

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



* Powering IBM Cloudant replication, optionally with a selector to filter some changes.
* Clients consuming the changes feed in batches but dealing with each change idempotently while not being concerned with sort order and expecting to see some changes more than one time.



The IBM Cloudant changes feed is not good for the following components:



* A message queue. For more information, see [IBM Messages for RabbitMQ](https://www.ibm.com/cloud/messages-for-rabbitmq) for managing queues.
* A message broker. For more information, see [IBM Event Streams](https://www.ibm.com/cloud/event-streams) for handling scalable, time-ordered streams of events.
* A real-time publish and subscribe system. For more information, see [IBM Databases for Redis](https://www.ibm.com/uk-en/cloud/databases-for-redis) for handling publish and subscribe topics.
* A transaction log.
* End of Marketing (EOM): 8 May 2020 After this date, Advanced Monitoring by Nimsoft is no longer available for purchase.
* End of Service (EOS): 8 July 2020 After this date, Advanced Monitoring by Nimsoft is no longer supported and usage is withdrawn by IBM Cloud.







 What happens if I can't make the transition on time? 

Advanced Monitoring by Nimsoft is available for purchase until 8 May 2020. After this date, IBM Cloud Monitoring supports all new monitoring purchases. For any resources with Advanced Monitoring by Nimsoft that were enabled before 8 May 2020, you can continue to use Advanced Monitoring by Nimsoft until support and usage is withdrawn on 8 July 2020. Failure to move your resource monitoring to IBM Cloud Monitoring by 8 July 2020 results in a gap in your resource monitoring.
This support adds the --extensions option to the subscription COS create, subscription COS update, subscription ping create, and subscription ping update commands. Also adds the --extensions-rm option to the subscription COS update and subscription ping update commands to remove CloudEvent extensions.<br> * Updated the project status on the output for the project get and the project list commands. The status of provisioning is changed to creating, and the status of pending reclamation is changed to soft deleted.<br> * Fixed various minor bugs.<br><br><br> 
 1.2.0 13 April 2021 <br><br> * New! Subscription support for jobs as a beta function. Added support for jobs as event destinations. Use the --destination-type option with the subscription ping create, subscription ping update, subscription cos create, and subscription cos update commands to specify the event destination. Valid values for this option are app and job.<br> * Updated the project get command to display project quota information.<br><br><br> 
 1.1.0 07 April 2021 <br><br> * Increased the polling frequency when build runs and job runs are waiting to complete.<br> * Updated the project delete command such that if a project was previously deleted without specifying the --hard option, a subsequent project delete command must use the --hard option.<br> * Updated the project select command such that a project must be in active status before it can be selected.<br> * Updated the output for the project list and project get commands to display projects that are in pending_reclamation status.<br><br><br> 
 1.0.0 30 March 2021 This version is the generally available release of Code Engine CLI.- Important Introduced a breaking change to Code Engine service binding functions. Service bindings that were created with releases of the CLI earlier than release 1.0.0 will no longer work after you update to the CLI 1.0.0 release. Unbind pre-existing service bindings before you update to CLI 1.0.0.<br><br><br><br> * Updated service bindings to use a new naming convention.
For more information about managing availability, see [How do I ensure zero downtime?](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-zero-downtime) 







 Change management 

Change management includes tasks such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management

 Task IBM responsibilities Your responsibilities 

 Update Delivery Pipeline images. Provide updated Delivery Pipeline job container images. These images might include updates to command tools (such as ibmcloud) that might affect the function of existing pipeline job scripts. Update Delivery Pipeline job scripts to respond to changes in underlying container images, or configure pipeline job scripts to use specific versions of container images instead of the latest version. 
 Deploy apps and other workloads by using the Delivery Pipeline. Maintain the Delivery Pipeline service. Maintain the job scripts that are run by the Delivery Pipeline service, the inputs to pipeline job stages (such as source code), and the apps and other workloads that are deployed by job scripts. 
 Support Delivery Pipeline private workers to allow pipeline workloads to run on customer infrastructure. Provide and maintain the private worker agent that integrates customer-managed infrastructure into the Delivery Pipeline service. Install the private worker agent into your Kubernetes cluster with enough capacity to run your pipeline workloads. Update the agent as new versions become available. 







 Identity and access management 

Identity and access management includes tasks such as authentication, authorization, access control policies, and approving, granting, and revoking access.



Table 3. Responsibilities for identity and access management

 Task IBM responsibilities Your responsibilities 

 Manage access to toolchains in resource groups and their associated IBM-hosted tools, except for Git Repos and Issue Tracking. N/A Grant, revoke, and manage access to toolchains by using IBM Cloud Identity and Access Management (IAM). For more information about access management, see [Managing user access to toolchains in resource groups](https://cloud.ibm.com/docs/services/ContinuousDelivery?topic=ContinuousDelivery-toolchains-iam-security).
Restoring a deprecated private product or version 

After you deprecate your product or version, your software enters a 90-day deprecation period before it is removed from users. During this 90-day deprecation period, you can't make changes to your product or version, but you can restore your product or version to its last published state. Your software cannot be restored after the 90-day deprecation period.

Complete the following steps to restore your product or version:



1.  In the IBM Cloud® console, click Manage > Catalogs > Private catalogs.
2.  Select the private catalog where your product is located.
3.  Select your product.
4.  Optionally, if you want to restore a specific version of your software, select that version from the list.

If your software has only one published version, and you restore that version, the entire product is restored.
5.  Open the Actions menu and select Restore product or Restore version.
6.  Click Yes.



You can also deprecate your product or version by clicking the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/actions-icon-vertical.svg) and selecting Restore for that product or version.
Time to find your team
<-- <ul> --> * From the Cloud Functions Actions]Actions page] ! ! ! ! page, select the action and then click Invoke. You can change the input parameter by selecting Change Input and then entering valid JSON in the following format:
{ "message": "xxxx" }

For example,

{ "message": "Time for a walk" }
<-- </ul> --><-- </section "id="section-periodic-slack-template-test" "> --><-- <section "id="section-periodic-slack-stop-trigger" "> --> Pausing or stopping your Periodic Slack Reminder trigger You can stop the Periodic Slack Reminder trigger in the following ways.<-- <ul> --> * From the console, go to the Triggers]] ! page and select the Periodic Slack Reminder trigger. Clear the selection for Enable. * From the CLI:
<-- <ul> -->

* Disable the rule by running the ibmcloud fn rule disable RULE_NAME]ibmcloud fn rule disable RULE_NAME] command where RULE_NAME is the name of the rule that you created for the Periodic Slack Reminder trigger. You can find rule names in your name space by running the ibmcloud fn rule list RULE_NAME]ibmcloud fn rule list RULE_NAME] command.
* Edit the trigger by running the ibmcloud fn trigger update]ibmcloud fn trigger update]!! ! ! ! ! !
* 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/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/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/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/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.
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. For example, you might have a user that needs to present a demonstration on your account for a few hours or a contractor that needs temporary access to a service over a couple days.

Complete the following steps to assign an access policy with a temporary time-based condition:



1. In the IBM Cloud console, go to Manage > Access (IAM)
2. Select Users, Trusted profiles, Service IDs, or Access groups, depending on the entity to which you want to assign access.
3. Click the entity's name from the list and go to Access.
4. Click Assign access.
5. Select a service and click Next.



* If you want the user to be able to create any service, select All Identity and Access enabled services.
* If you want to assign the user access to a specific service, select it from the list.



6. Select the resource that you want to assign the user access to, or select All resources. Click Next.
7. (Optional) Select a resource group access role. Click Next.
8. Select any combination of service access and platform access roles, and click Next.
9. Click Add condition and select One-time.
10. Select the time zone.



As an example, let's say that you're creating a conditional policy for a developer that is based in Dublin. In this case, select UTC+1 so that the date and time range that you select in the next step enforces access at the right time for that location.



1. Complete the fields for the date and time range that that determines when the condition grants and terminates access.
2. Click Create.
3. Click Review.
4.