vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud ce app create --name kafka-sender-app --image icr.io/codeengine/kafka-sender --env-from-secret kafka-subscription-secret --env BROKERS=broker-4-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --min-scale 1



3. After you deploy this app, run the app get command to confirm that the app is in ready status.

ibmcloud ce app get -n kafka-sender-app



You created the kafka-sender-app app to produce Kafka messages for Code Engine event subscriptions, and you created the kafka-subscription-secret secret that contains the required credentials.





 Step 3: Setting up a Code Engine Kafka subscription 

For Code Engine to work with Kafka events, set up a Code Engine Kafka eventing subscription to connect to Kafka event brokers and listen for Kafka events. Also, set up a Code Engine app to act as the receiver of the Kafka events. The Kafka event subscription defines the relationship between the Kafka producer (sender) and consumer (receiver) of events.

The Code Engine Kafka event subscription connects to your Kafka message broker and sends HTTP Post requests for each incoming Kafka message to the receiver application. For more information about the information that is included with Kafka events, see [HTTP headers and body information for events that are delivered to apps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-working-kafkaevent-producersubkafka-headerbody-app).



1. Create a Code Engine application to act as an event consumer of Kafka messages and receive the Kafka events. For example, create an application that is called kafka-receiver-app that uses the icr.io/codeengine/kafka-receiver image.
event-notifications.00016I INFO The Microsoft Teams destination is successfully served. Response from the microsoft teams API: OK with the status code: 200 
 event-notifications.00001W WARN A notification event from source<Source_ID> is rejected because no topic is configured for the source. . The topic to filter the event is missing. 
 event-notifications.00002W WARN A notification event from the source <Source_ID> is invalid as it is not filtered by any topic. 
 event-notifications.00003W WARN A notification request with ID <NOTIFICATION-ID>, that is processed by the following subscribers: [<LIST-OF-SUBSCRIPTIONS>], is forbidden for the destination type: smtp_ibm/sms 
 event-notifications.00004W WARN A notification with ID <NOTIFICATION_ID> is not dispatched as it has no subscribers. 
 event-notifications.00005W WARN Webhook returned with an error response: Not Found with the status code: 404 
 event-notifications.00006W WARN Slack returned with an error response: <error_message> with the status code: 404 
 event-notifications.00007W WARN Microsoft teams API returned with an error response: Not Found with the status code: 401 
 event-notifications.00008W WARN The SMS is not delivered because it is unsubscribed by: [<SMS_NUMBERS>] 
 event-notifications.00001E ERROR Notifications failed to dispatch to the following invalid devices [<DEVICE_IDS>] and platform push_android. 
 event-notifications.00002E ERROR Webhook returned with an error response:<Error response> Unauthorised with the status code:404 
 event-notifications.00003E ERROR Notification dispatch failed due to the authentication error for device id <device_id> and platform <platform_name>. 
 event-notifications.00004E ERROR Slack returned with an error response: <error_message> with the status code: 401 
 event-notifications.00005E ERROR Notification dispatch failed due to the <'BadDeviceToken'> error for device id <device_id> and platform <platform_name>.
Create an application that is named cos-app with the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command by using an image that is called cos-listen. This app logs each event as it arrives. This image is built from cos-listen.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/cos-event).

ibmcloud ce app create --name cos-app --image icr.io/codeengine/cos-listen

Run ibmcloud ce application get --name cos-app to verify that your app is in a Ready state. The application is in a ready state if the status summary reflects that the application deployed successfully.

For more information about this app, see the [IBM Cloud Object Storage readme file](https://github.com/IBM/CodeEngine/tree/main/cos-event).





 Step 4: Create a subscription 

After your app is ready, you can create an Object Storage subscription so you can start receiving Object Storage events with the [ibmcloud ce sub cos create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-create) command.

For example, create an Object Storage subscription that is called cos-sub. This subscription forwards any type of bucket operation from the mybucket bucket to an application that is called cos-app.

ibmcloud ce sub cos create --name cos-sub --destination cos-app --bucket mybucket --event-type all

Run the ibmcloud ce sub cos get -n cos-sub command to find information about your subscription.

Example output

By default, the [ibmcloud ce sub cos get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get) command returns two parts.
To schedule an event for every Friday at midnight, specify 0 0 * * FRI.

For more information about crontab, see [CRONTAB](http://crontab.org/).

You can set your cron interval by using the --schedule option with the subscription cron command, as shown in Step 3. If you do not specify the --schedule option, then by default, the cron event is sent every minute of every day.





 Step 2: Create your app (or job) 

While events can be used to trigger apps or jobs, this tutorial uses an app.

Create your application called cron-app with the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command. This app pulls an image that is called icr.io/codeengine/cron. This app logs each event as it arrives, showing the full set of HTTP Headers and HTTP Body payload. For more information about the code that is used for this example, see [cron](https://github.com/IBM/CodeEngine/tree/main/cron).

ibmcloud ce app create --name cron-app --image icr.io/codeengine/cron

Run ibmcloud ce application get --name cron-app to verify that your app is in a Ready state.

You can find more information about this app at [cron readme file](https://github.com/IBM/CodeEngine/tree/main/cron).





 Step 3: Create a subscription 

After your app is ready, create a subscription to the cron event producer and connect it to your app with the [ibmcloud ce sub cron create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-create) command.

The following example creates a cron subscription that is called cron-sub and specifies the cron-app application as its destination.
06 December 2021 

Review the release notes for 06 December 2021.

IBM Cloud Object Storage subscriptions
: Added support for IBM Cloud Object Storage eventing subscriptions from the Code Engine console. See [Working with the IBM Cloud Object Storage event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producer).

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





 01 December 2021 

Review the release notes for 01 December 2021.

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







 November 2021 

Review the release notes for November 2021.



 19 November 2021 

Review the release notes for 19 November 2021.

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





 16 November 2021 

Review the release notes for 16 November 2021.

Code Engine supports virtual private endpoints.
: Added support for integration of Code Engine projects with IBM Cloud® Virtual Private Endpoints (VPE) for Virtual Private Cloud (VPC). You can use this support to connect from your VPC network to Code Engine applications. See [Using Virtual Private Endpoints with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-vpe) and [Options for visibility for a Code Engine application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-application-workloadsoptionsvisibility).

CLI version 1.23.0 released.
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).
For Event type, select the Periodic timer tile. Click Next.
2. For General, provide a name for the Periodic timer subscription, for example, myptimer. You can optionally provide event attributes. Note that if the Periodic timer event consumer is an application, event attributes are available as HTTP headers. If the event consumer is a job, event attributes are available as environment variables. Click Next to proceed.
3. For Schedule, provide information about the timing of the events. The Periodic timer (cron) event producer uses standard crontab syntax to specify interval details. Choose your interval from the provided patterns or provide your own custom cron expression, such as 0 0 * * , which specifies for the event to occur every day at midnight. For this example, select the schedule pattern for every day, every hour, every minute. Notice that the cron expression is generated for you. The day, hour, and minute patterns and the Cron expression are in Coordinated Universal Time (UTC). If you do not specify a schedule, then this event subscription sends an event every minute. A list of upcoming scheduled events is displayed. Notice that these upcoming scheduled events are displayed in your time zone. Click Next to proceed.
4. For Custom event data, provide data to include in the body of your event message. You can specify the message as plain text or in base64 format. For this example, specify the text, hello stranger as the body of the event message. If the message is in base64 format, you can choose to have the message decoded when the event is sent. You can also specify the content type for your custom event data. Click Next to proceed.
5. For Event consumer, specify the application or job to receive events. Notice that you can choose from a list of defined applications and jobs. For this example, use the myapp application that references the icr.io/codeengine/cron image.
apiconnect.credential_createSpaceInitiated.create Create a Application Credential object 
 apiconnect.credential_clearSpaceInitiated.delete Clear the Application Credential objects 
 apiconnect.credential_updateSpaceInitiated.update Update the Application Credential object by name or ID 
 apiconnect.credential_delSpaceInitiated.delete Delete the Application Credential object by name or ID 
 apiconnect.credential_resetSpaceInitiated.create Reset the client id and client secret 
 apiconnect.credential_resetClientSecretSpaceInitiated.create Reset the client secret 
 apiconnect.credential_verifyClientSecretSpaceInitiated.create Verify the client secret 
 apiconnect.subscription_create.create Create a Subscription object 
 apiconnect.subscription_clear.delete Clear the Subscription objects 
 apiconnect.subscription_update.update Update the Subscription object by name or ID 
 apiconnect.subscription_del.delete Delete the Subscription object by name or ID 
 apiconnect.subscription_createSpaceInitiated.create Create a Subscription object 
 apiconnect.subscription_clearSpaceInitiated.delete Clear the Subscription objects 
 apiconnect.subscription_updateSpaceInitiated.update Update the Subscription object by name or ID 
 apiconnect.subscription_delSpaceInitiated.delete Delete the Subscription object by name or ID 
 apiconnect.draft_clear.delete Clear the Draft objects 
 apiconnect.draft_introspectWsdl.create Introspect the WSDL 
 apiconnect.draft_product_create.create Create a Draft Product object 
 apiconnect.draft_product_clearAll.delete Clear all Draft Product objects in all collections 
 apiconnect.draft_product_clear.delete Clear the Draft Product objects 
 apiconnect.draft_product_update.update Update the Draft Product object by ID 
 apiconnect.draft_product_del.delete Delete the Draft Product object by ID
[Using certificates from an external Certificate Authority](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-tutorial-extca)Using certificates from an external Certificate Authority

In this tutorial, you learn how to use certificates that were generated by an external Certificate Authority (CA) with your IBM® Blockchain Platform network. After you gather the required certificates for a peer or ordering node, you build a Membership Service Provider (MSP) definition that is used by your blockchain components.

IBM Blockchain Platform



* 30 minutes
* 2023-02-17



Compute[Getting started with Cloud for Education Applications Lab](https://cloud.ibm.com/docs/cloud-for-education?topic=cloud-for-education-getting-started-applications-lab)Getting started with Cloud for Education Applications Lab

IBM Cloud for Education Applications Lab Provides a powerful customized portal for students & faculty members where applications images can be launched or accessed via a services catalogue on a single pane of glass. It is a public cloud service but able to integrate with academic institution's private or on-premise lab environment as a hybrid compute model. Students and faculty members can access the virtual desktops and application from any place, any time and on any device.

IBM Cloud for Education



* 2021-03-18



[Getting started with IBM Cloud for Education Virtual Course Credit ](https://cloud.ibm.com/docs/cloud-for-education?topic=cloud-for-education-getting-started-virtual-course-credit)Getting started with IBM Cloud for Education Virtual Course Credit

IBM Cloud for Education Virtual Course Credit allows users to utilize lab hours from services supporting Course Credit transactions . Users can purchase IBM Cloud for Education Virtual Course Credit by selecting the IBM Course Credit Subscription Plan

IBM Cloud for Education



* 2021-03-31



[Deploying and scaling applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-app-tutorial)Deploying and scaling applications

With this tutorial, deploy an application with the Code Engine CLI. The application scales to zero when not in use.

Code Engine



* 10 minutes
This sample sender app requires the password credentials that are stored in your kafka-subscription-secret, and it requires the BROKERS environment variable.
* Specify the --env-from-secret option to reference the full secret, kafka-subscription-secret, which contains the password credentials.
* Specify the --env option to add a literal environment variable, BROKERS, and provide the name of one of the broker hosts that are listed in the details of the service credentials in the Event Streams service instance. However, if you want to specify more than one broker hostname, use the format --env BROKERS-broker1,broker2,broker3.
* (optional) Specify the --min-scale=1 option so that the app always has an instance that is running and does not scale to zero. Configuring the app to always have a running instance is useful when you view logs. If you are running in a production environment, consider the cost of keeping a running instance of your app or whether you want Code Engine to autoscale to zero. By default, the app scales to zero when not in use.



ibmcloud ce app create --name kafka-sender-app --image icr.io/codeengine/kafka-sender --env-from-secret kafka-subscription-secret --env BROKERS=broker-4-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --min-scale 1













 Setting up Code Engine to receive Kafka events for an app 

For Code Engine to work with Kafka events, use the console or CLI to set up a Code Engine Kafka eventing subscription to connect to Kafka event brokers and listen for Kafka events. Also, set up a Code Engine app (or job) to act as the receiver of the Kafka events. The Kafka event subscription defines the relationship between the Kafka producer (sender) and consumer (receiver) of events.

The Code Engine Kafka event subscription connects to your Kafka message broker and sends HTTP Post requests for each incoming Kafka message to the receiver application.
Troubleshooting Red Hat OpenShift problems 

Use the troubleshooting information to diagnose and fix problems with Red Hat® OpenShift®.



 RHEL subscription 

If you encounter a problem with your subscription, use the following command to run a query.

subscription-manager list --available --all





 Load-balancer 

To check that load balancing is working, use the following command from the bastion node. Load balancing is successful if the result is a full set of headers.

wget --no-check-certificate https://api.ocp.dallas.ibm.local:6443





 Red Hat CoreOS 

You do not need to connect by using SSH to node, but if you need to, you can do so through the bastion node. The following example connects to the bootstrap server by using the following command:

ssh core@192.168.133.9

If you get an error, then try the following commands that disable the checking of the fingerprint:

ssh -o StrictHostKeyChecking=no core@192.168.133.9

This example shows how to connect to control-plane node from the bastion node to view the logs and change the permission to make them readable. The directory name might be different.

ssh -i /root/.ssh/id_rsa core@192.168.133.12
sudo su
chmod 777 /var/log/pods/b2810e842791d83d48a4684295b7cd01/etcd-member/0.log

This example shows how to download the log to the bastion node and then on to the jump-server or remote device for readability and the ability to parse the logs. The directory name might be different.

scp -i /root/.ssh/id_rsa core@192.168.133.10:/var/log/pods/b2810e842791d83d48a4684295b7cd01/etcd-member/0.log 0.log





 Red Hat OpenShift 

Gets a list of nodes and their status:

oc get nodes
kubectl get subscriptions.operators.coreos.com -A
6. If you find CRs, determine whether you still need these resources.



* You might still see the olm-operators and ibm-operators operator groups that were deployed by OLM. These operator groups were part of the installation of OLM. Because you do not have any cluseterserviceversions instances in the previous steps, you are no longer using these operator groups.
* If you had version 1.4 - 1.9 of the Istio add-on installed in the past, you might still see the istiooperators.operators.coreos.com resource in the ibm-operators namespace. If you upgraded Istio to at least version 1.10, then you no longer need this resource.
* If you find other CRs, chances are you are not using them because you didn't have any clusterserviceversions instances in the previous steps. However, review each CR with your cluster admin on a case-by-case basis to determine whether they are still being used.



The following steps assume you've completed the review and guide you through deleting OLM.
7. If you determined that OLM is not used by the Istio add-on or any additional operators, run the following commands separately to delete OLM resources.

kubectl delete clusterrole aggregate-olm-edit
kubectl delete clusterrole aggregate-olm-view
kubectl delete deploy -n ibm-system catalog-operator
kubectl delete deploy -n ibm-system olm-operator
kubectl delete clusterrole system:controller:operator-lifecycle-manager
kubectl delete serviceaccount -n ibm-system olm-operator-serviceaccount
kubectl delete clusterrolebinding olm-operator-binding-ibm-system
kubectl delete operatorgroup -n ibm-operators ibm-operators
kubectl delete operatorgroup -n ibm-system olm-operators
kubectl delete service -n ibm-system catalog-operator-metrics
: See [Getting started with subscriptions](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribing-events), [Working with the Ping event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cron), and [Working with the IBM Cloud Object Storage event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producer).





 8 June 2021 

Review the release notes for 8 June 2021.

New region!
: Code Engine is supported in a new region: Asia Pacific Osaka (jp-osa). See [Regions for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-regions).





 3 June 2021 

Review the release notes for 3 June 2021.

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

Deleting data
: Added information about hard and soft deletes of data in Code Engine projects. See [Deleting your data in Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-mng-datadata-delete).







 May 2021 

Review the release notes for May 2021.



 27 May 2021 

Review the release notes for 27 May 2021.

CLI version 1.7.0 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).

Updated information about supported IBM Cloud Object Storage buckets for subscriptions.
Schematics Agents are a [beta feature](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-beta-limitations) that are available for evaluation and testing purposes. It is not intended for production usage. Refer to the list of [limitations for Agent](https://cloud.ibm.com/docs/schematics?topic=schematics-agent-beta-limitations) in the beta release.



 Why are you getting create endpoint gateway failure with wrong number of segments in CRN? 

 What’s happening 

When you run an IBM Cloud Schematics plan or apply action, Schematics Workspaces produces the endpoint gateway that is failed with wrong number of segments in CRN. Following error message is received.

2022/05/31 12:19:31 Terraform apply | Error: Create Endpoint Gateway failed wrong number of segments in CRN
2022/05/31 12:19:31 Terraform apply | {
2022/05/31 12:19:31 Terraform apply | "StatusCode": 400,
2022/05/31 12:19:31 Terraform apply | "Headers": {
2022/05/31 12:19:31 Terraform apply | "Cache-Control": [
2022/05/31 12:19:31 Terraform apply | "max-age=0, no-cache, no-store, must-revalidate"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Cf-Cache-Status": [
2022/05/31 12:19:31 Terraform apply | "DYNAMIC"
2022/05/31 12:19:31 Terraform apply | ],
2022/05/31 12:19:31 Terraform apply | "Cf-Ray": [
2022/05/31 12:19:31 Terraform apply | "713fa8882c4b9f0a-DFW"
2022/05/31 12:19:31 Terraform apply | ],
2021/12/06 10:15:49 Terraform apply | TASK [Gathering Facts] 
2021/12/06 10:15:49 Terraform apply | fatal: [161.156.161.7]: FAILED! => {"msg": "winrm or requests is not installed: No module named 'winrm'"}
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply | PLAY RECAP 
2021/12/06 10:15:49 Terraform apply | 161.156.161.7 : ok=0 changed=0 unreachable=0 failed=1 skipped=0 rescued=0 ignored=0
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:49 Terraform apply | with null_resource.schematics_for_windows,
2021/12/06 10:15:49 Terraform apply | on schematics.tf line 2, in resource "null_resource" "schematics_for_windows":
2021/12/06 10:15:49 Terraform apply | 2: provisioner "ansible" {
2021/12/06 10:15:49 Terraform apply 
2021/12/06 10:15:50 Terraform APPLY error: Terraform APPLY errorexit status 1
2021/12/06 10:15:50 Could not execute action

WinRM is not supported by Schematics Terraform Ansible provisioner. Alternatively you can use the Schematics Actions to run the Ansible playbooks with WinRM. The Schematics Actions support [WinRM](https://cloud.ibm.com/docs/schematics?topic=schematics-action-working).





 When are the new Terraform and Ansible versions added to Schematics? 

After new Terraform and Ansible versions are released by the community, the IBM team begins hardening and testing the release for Schematics.