vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why can't I validate my Terraform template? 

When you try to onboard a Terraform template to the IBM Cloud® catalog, the validation process fails because the correct version of the Terraform template isn't specified.

  What’s happening 

The following error is displayed when you try to validate that the Terraform template can be installed on the target infrastructure:

> Error: Error parsing /file-path/main.tf: At 9:14: Unknown token : 9:14 IDENT var.resource_group

  Why it’s happening 

The Terraform version that you specify during the validation process is incorrect. You might be specifying a version of Terraform that's used when you run stand-alone IBM Cloud Schematics.

  How to fix it 

To specify the Terraform version to use during the validation process, complete the following steps:



1.  Add a variable to your Terraform template as shown in the following example:

variable "TF_VERSION" {
description = "terraform version."
default = 0.13
}
2.  After you import your Terraform template to your private catalog, add the template version as a deployment value that's hidden from users when they install the software.
Therefore, you need to select a peer from the drop-down list that is from an organization that was a member of the channel before the smart contract was last instantiated on the channel.
4. If you want to associate a private data collection configuration file with the smart contract you can upload the JSON file. Or if you want to update an existing collection configuration, you can upload the JSON file. If the smart contract was previously instantiated with a collection configuration file, you must again upload the previous version or a new version of the collection configuration file during this step.
5. (Optional) Modify the smart contract initialization argument values if the parameters have changed. If you are unsure about it, check with your smart contract developer. If they have not changed, you can leave this field blank.





After you upgrade the smart contract, you will change the version of the contract that is instantiated on the channel. If you are using private data collections, be sure you have configured anchor peers on the channel.





 Considerations when you upgrade smart contracts 



1. Do I need to install the new version of the smart contract on all my peers?

When a smart contract is invoked on a peer, it attempts to run the version that is instantiated on the channel. If a previous version is running on the peer, it results in an error. Therefore, before you upgrade a smart contract on a channel, it is a best practice to install the latest version of the smart contract on all peers that are running the previous version.
2. Can a subsequent smart contract version still process data on the ledger from a prior version of the smart contract?

Yes. As long as the new smart contract code addresses the data in a compatible way (by adding new JSON fields and not changing the semantics or type of the existing fields), any subsequent version of the smart contract can run against the data from a prior version.
3. What happens to my peers if I forget to upgrade them to the latest version before updating the smart contract on the channel?

After updating the channel to use the new version of the smart contract, if there are still peers on the channel running the previous version, those peers are no longer able to endorse transactions for the smart contract.
This tool is optional and it can be used on the jump-server or remote device to enable the use of PowerCLI. For more information, see [PowerShell Core](https://github.com/PowerShell/PowerShell).
* PowerCLI - PowerCLI is a PowerShell interface for managing VMware vSphere®. You can automate all aspects of vSphere management, including network, storage, VMs, and guest OS. This tool is optional and it can be used on the jump-server or remote device to help the preparation of the vCenter Server instance. These steps can be done by using the GUI. For more information about how to install this tool, see [Install PowerCLI](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.esxi.install.doc/GUID-F02D0C2D-B226-4908-9E5C-2E783D41FE2D.html).
* PowerNSX - PowerNSX is a PowerShell module that abstracts the VMware NSX API to a set of easily used PowerShell functions. This tool is optional and it can be used on the jump-server or remote device to help the preparation of NSX on the vCenter Server instance. These steps can be done by using the GUI. For more information, see [PowerNSX](https://github.com/vmware/powernsx).







 Build process overview 

This documentation describes the process to install Red Hat OpenShift v4.7 on to an existing vCenter Server instance. The process installs and configures:



* One bastion node.
* One bootstrap node.
* Three control plane nodes.
* Three worker nodes.



The deployment approach is described in the following phases:



* Phase 1 - vCenter Server instance preparation.
Note: An ICN is not required for evaluation storage. For more information on how to find your ICN, see [What is my IBM Customer Number (ICN)?](https://www.ibm.com/support/pages/what-my-ibm-customer-number-icn) Conditional None 
 remote_cidr_blocks Comma-separated list of IP addresses that can access the Spectrum Scale cluster bastion node through SSH. For security purposes, provide the public IP addresses assigned to the devices that are authorized to establish SSH connections (for example, 169.45.117.34). To fetch the IP address of the device, use [https://ipv4.icanhazip.com/](https://ipv4.icanhazip.com/). Yes None 
 resource_group Resource group name from your IBM Cloud account where the VPC resources should be deployed. For more information, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs). No Default 
 resource_prefix Prefix that is used to name the IBM Cloud resources that are provisioned to build the Spectrum Scale cluster. Make sure that the prefix is unique since you cannot create multiple resources with the same name. The maximum length of supported characters is 64. No spectrum-scale 
 storage_bare_metal_osimage_name Name of the image that you would like to use to create the storage cluster nodes for the Spectrum Scale cluster. The solution supports only a RHEL 8.4 stock image. No ibm-redhat-8-4-minimal-amd64-3 
 storage_bare_metal_server_profile Specify the bare metal server profile type name to be used to create the bare metal storage nodes. For more information, see [Bare metal server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile). No cx2d-metal-96x192 
 storage_cluster_filesystem_mountpoint Spectrum Scale storage cluster (owningCluster) file system mount point.
Then, these hosts provide the compute power to run IBM Cloud services, such as workloads in managed Red Hat OpenShift clusters or data and artificial intelligence (AI) tools like Watson.

Your Satellite location includes tools such as Satellite Link and Satellite Config to provide additional capabilities for securing and auditing network connections in your location and consistently deploying, managing, and controlling your apps and policies across clusters in the location.

For more information, see the [Satellite product page](https://www.ibm.com/product/satellite).
* Where is Satellite available?

Because you bring your own compute host infrastructure to your Satellite location, you can choose to host this infrastructure anywhere you need it. However, to monitor malicious activity and apply updates to your location, these compute hosts are managed by an IBM Cloud multizone region that is supported by IBM Cloud Satellite. You can choose any of the supported regions, but to reduce latency between IBM Cloud and your Satellite location, choose the region that is closest to your compute hosts.

For more information, see [Supported IBM Cloud locations](https://cloud.ibm.com/docs/satellite?topic=satellite-sat-regions).
* Is my location setup highly available?

The IBM Cloud Satellite service architecture and infrastructure is designed to ensure reliability, low processing latency, and a maximum uptime of the service. By default, every location is managed by a highly available Satellite control plane that consists of a control plane master and worker nodes. For an overview of potential points of failures and your options to increase the availability of your location and control plane, see [High availability for IBM Cloud Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-ha).
* What happens if my Satellite control plane becomes unavailable?

Every location is securely connected to the IBM Cloud multizone region that manages your location by using the Satellite Link component. The link component runs in your control plane and is the main gateway for any communication between your Satellite location and IBM Cloud. If your Satellite location cannot communicate with the IBM Cloud multizone region anymore, your existing location workloads will continue to run, but you cannot make any configuration changes or roll out updates to the services and apps that run in your location.
The following example displays the logs of a specific instance of a job run. Use the jobrun get command to obtain the name of the job run instances.

ibmcloud ce jobrun logs --instance myjobrun-3-0





 Example output 

Getting logs for job run instance 'myjobrun-3-0'...
OK

myjobrun-3-0/myjobrun:
Hi from a batch job! My index is: 3





 Example of logs of all instances of a job run 

The following example displays the logs of all the instances of a job run.

ibmcloud ce jobrun logs --jobrun myjobrun



 Example output of logs of all instances of a job run 

Getting logs for all instances of job run 'myjobrun'...
Getting jobrun 'myjobrun'...
Getting instances of jobrun 'myjobrun'...
OK

myjobrun-1-0/myjobrun:
Hi from a batch job! My index is: 1

myjobrun-2-0/myjobrun:
Hi from a batch job! My index is: 2

myjobrun-3-0/myjobrun:
Hi from a batch job! My index is: 3

myjobrun-4-0/myjobrun:
Hi from a batch job! My index is: 4

myjobrun-5-0/myjobrun:
Hi from a batch job! My index is: 5









 ibmcloud ce jobrun restart 

Restart running job run instances.

ibmcloud ce jobrun restart (--instance JOBRUN_INSTANCE | --jobrun JOBRUN_NAME) [--quiet]



 Command Options 

--instance, -i
: The name of a specific job run instance. Use the jobrun get command to find the instance name. This value is required if --jobrun is not specified.

--jobrun, -j, --name, -n
: Restart all the running instances of the specified job run.
PKCS #11 is a cryptographic standard for secure operations, generation, and storage of keys. See [Configuring a node to use a Hardware Security Module (HSM)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-cfg-hsm) to learn more.





 Can I integrate my corporate LDAP server with the Certificate Authority (CA) in the IBM Blockchain Platform? 

You cannot currently directly integrate your LDAP server with the CA. However, you can use an external mechanism to generate X.509 certificates for the LDAP users. To use those certificates with a peer or ordering service, see these topics on [Using certs from an external CA for your peer or ordering service](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-adv-deploymentibp-console-adv-deployment-third-party-ca) and [Manually building an organization MSP](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-organizationsconsole-organizations-build-msp).

Also, you cannot configure the blockchain console login authentication to use an LDAP user registry at this time.





 What is the process for rotating certificates on a periodic basis? 

Similar to how passwords need to be regularly updated, identity certificates need to be renewed, a process also referred to as "certificate rotation". The platform displays certificate expiration dates for components throughout the console. When a certificate expires, transactions on the network will fail because the identity can no longer be trusted. It is your responsibility to monitor those expiration dates and manage your certificate renewal accordingly. The process varies depending on the type of certificate, when it was generated, and for organization admin certificates, whether Node OU support was enabled on the MSP when the identity was enrolled. The platform attempts to renew the peer and ordering node enrollment certificates 30 days before they expire.
During instance [create](https://cloud.ibm.com/apidocs/vpccreate-instance) or [update](https://cloud.ibm.com/apidocs/vpcupdate-instances), the host_failure sub-property can be used to set the host failure availability_policy of the virtual server instance. If the compute host experiences a failure, specify restart or stop to set the policy.



Table 2. Recovery policy API

 Host failure policy Attribute 

 restart 'restart' 
 stop 'stop' 



For more information, see [Create an instance](https://cloud.ibm.com/apidocs/vpccreate-instance) and [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances&interface=api).





 Next steps 

For more information about planned and unplanned host outages, see the FAQ [In what cases is my virtual server migrated to a different host?](https://cloud.ibm.com/docs/vpc?topic=vpc-faqs-for-vsisfaq-vsi-13).
Your IBM customer number is used for identification purposes during your registration process with the IBM Invoices page and during other interactions with [IBM Support](https://www.ibm.com/support/home/).

To ensure that access is granted to the correct individuals, you must register using an email address that includes your company's domain, such as ibm.com. Requests using personal, non-company-specific email addresses might not be approved. In these cases, contact the [IBM Cloud Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).



1. Go to [Invoices@IBM](http://ibm.com/invoices), and select your region.
2. Log in with the same IBMid and password that you use to log in to IBM Cloud.
3. Complete your profile on the Invoices@IBM website.
4. From the Active and pending accesses tab, add access to your account and provide your IBM customer number.

If you don't know, or the website does not accept your customer number, contact IBM Cloud Support by calling 1-866-325-0045 and selecting the third option, or contact the [eCustomer Care team](https://www-112.ibm.com/software/howtobuy/passportadvantage/paocustomer/docs/en_US/ecare.html).



To access your invoices in the future, you can click the link from the Invoices page in the console or bookmark the external website to go to it directly.







 Requesting paperless invoices 

Depending on which region your account is located in, you can switch to paperless invoicing by submitting a request in writing through the IBM Customer Support site. Paperless invoicing isn't available in all regions.



1. Go to [IBM Customer Support](https://www.ibm.com/support/customer/zz/en/selectcountrylang.html), and select your region.
2. Click Contact us.
3. Click Email us in the Invoice, payment section.
4.
Why my email notifications sent didn’t reach customers even though in the logs I can see successfully sent notifications? 

This may be due to your Event Notifications instance has a subscription created for the smtp_ibm destination and has no email ID added as a recipient to the list for the subscription.

Make sure your Event Notifications instance has a subscription created for the smtp_ibm destination and has at least one email ID added as a recipient to the list for the subscription.





 Is it possible to send notifications to more than one destination using Event Notifications? 

Yes. You can send notifications to more than one destination.
CE_TIME=2021-04-13T17:41:00.429658447Z
CE_TYPE=dev.knative.sources.ping









 Defining additional event attributes 

When you create a subscription, you can define additional event attributes to be included in any events that are generated. These event attributes appear similar to any other CloudEvent attribute in the event delivery. If you choose to specify the name of an existing CloudEvent attribute, then it overrides the original value that was included in the event. For more information, see [Can I use other CloudEvents specifications?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-cloudevents)

From the console, you can specify event attributes as key-value pairs from the General tab for your Periodic timer (cron) event subscription.

With the CLI, to define additional attributes, use the --extension options with the [ibmcloud ce sub cron create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-create) CLI command.





 Deleting a subscription 

When you no longer need a Periodic timer (cron) subscription, you can delete it.



 Deleting a subscription from the console 



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.
3. From the list of subscriptions, delete the subscription that you want to remove from your application or job.



If you delete an app or a job, the subscription is not deleted.





 Deleting a subscription with the CLI
CE_TYPE=com.ibm.cloud.cos.document.delete









 Defining additional event attributes 

When you create a subscription, you can define additional CloudEvent attributes to be included in any events that are generated. These attributes appear similar to any other CloudEvent attribute in the event delivery. If you choose to specify the name of an existing CloudEvent attribute, then it overrides the original value that was included in the event.

To define addition attributes, use the --extension options with the [ibmcloud ce subscription cos create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-create) CLI command.

For more information, see [Can I use other CloudEvents specifications?](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-cloudevents)





 Deleting a subscription 

When you no longer need an IBM Cloud Object Storage subscription, you can delete it.



 Deleting a subscription from the console 



1. From the [Code Engine Projects page](https://cloud.ibm.com/codeengine/projects), go to your project.
2. From the Overview page, click Event subscriptions to view a listing of defined subscriptions.
3. From the list of subscriptions, delete the subscription that you want to remove from your application or job.



If you delete an app or a job that is associated with the subscription, the subscription is not deleted. If you re-create the application or job (or another app or job with the same name), your subscription reconnects with the app or job.





 Deleting a subscription with the CLI 

You can delete an IBM Cloud Object Storage subscription by running the [ibmcloud ce subscription cos delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-delete) command.

For example, use the following command to delete an IBM Cloud Object Storage subscription that is called mycosevent,
: See [API change log](https://cloud.ibm.com/docs/codeengine?topic=codeengine-api-changelog).





 25 May 2023 

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).

Updated information about DDoS protection in Code Engine
: See [DDoS protection](https://cloud.ibm.com/docs/codeengine?topic=codeengine-securesecure-ddos).

Added troubleshooting information for app connectivity
: See [Why does my app connection fail](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-app-connection-fail)?

Updated information about applying filters on Log Analysis data
: See [Can I apply filters on Log Analysis data](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logsview-logs-filters)?





 18 May 2023 

Added troubleshooting information for job runs not starting
: See [Why is my job run not starting](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-jobrun-notstart)?

Added troubleshooting information for unavailable details of service binding operations
: See [Why can't I display details of my configured service binding operations](https://cloud.ibm.com/docs/codeengine?topic=codeengine-ts-sb-projsettings-nodetails)?





 16 May 2023 

CLI version 1.43.5 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated versions for buildpacks
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).
Changing your Db2 Warehouse entitlements to a Cloud Pak for Data SaaS Subscription 

Migrating your stand-alone parts to a Cloud Pak for Data subscription gives you more flexibility to choose which offerings you want to consume, and how much you want to consume.

A subscription allows you to buy credits that you can use as quickly or slowly as you want to, based on your changing needs. If you want to provision a new instance or scale up storage or compute for an existing instance, you can initiate the request within minutes, without the need for a charge agreement to be created or amended. A subscription also provides you with the opportunity to explore a larger portfolio of offerings.



  Steps 



1.  Purchase an IBM Cloud Pak for Data as-a-Service subscription.
2.  Apply this subscription to the IBM Cloud account that currently contains your Db2 Warehouse on Cloud instance.
3.  Create a case with support ([https://cloud.ibm.com/unifiedsupport/supportcenter](https://cloud.ibm.com/unifiedsupport/supportcenter)) and request to have your instance converted to use this subscription.
: See [Choosing a build strategy](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-strategy).





 4 May 2021 

Review the release notes for 4 May 2021.

New region!
: Code Engine is supported in a new region: EU Great Britain (eu-gb). See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).







 April 2021 

Review the release notes for April 2021.



 29 April 2021 

Review the release notes for 29 April 2021.

Added metrics for jobruns to information about monitoring in Code Engine.
: See [Monitoring for Code Engine - Total number of jobruns](https://cloud.ibm.com/docs/codeengine?topic=codeengine-monitoribm_codeengine_jobruns).

CLI version 1.4.0 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 21 April 2021 

Review the release notes for 21 April 2021.

CloudEvents specification
: Added information about support for CloudEvents specification. See [Can I use other CloudEvents specifications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-eventssubscribing-events-cloudevents)?

CLI version 1.3.0 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).





 14 April 2021 

Review the release notes for 14 April 2021.

New! Subscription support for jobs as a beta function.
: Revised subscription information to describe how your Code Engine applications or jobs can receive events by subscribing to event producers.