vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Environment variables for events that are delivered to jobs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-envir-variables-cron)



* [Defining additional event attributes](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronadditional-attributes-cron)
* [Deleting a subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsubscription-delete-cron)



* [Deleting a subscription from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsubscription-delete-cron-ui)
* [Deleting a subscription with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsubscription-delete-cron-cli)





[Working with the IBM Cloud Object Storage event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producereventing-cosevent-producer)



* [Setting up the IBM Cloud Object Storage event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producersetup-cosevent-producer)
* [Assigning the Notifications Manager role to Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producernotify-mgr-cos)
* [Subscribing to IBM Cloud Object Storage events for an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producerobstorage_ev_app)
: 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.
: See [Set up the IBM Cloud Object Storage event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producersetup-cosevent-producer).

Added information about specifying the --path option when you create a subscription to an application.
: See [Subscribing to Ping events for an app](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-croneventing-cron-existing-app) and [Creating an IBM Cloud Object Storage subscription for an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-eventing-cosevent-producerobstorage_ev_app).

Updated information about accessing container registries.
: See [Accessing container registries](https://cloud.ibm.com/docs/codeengine?topic=codeengine-add-registry).

Added information about working with Kubernetes and Code Engine.
: See [Using Kubernetes with Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-kubernetes).





 18 May 2021 

Review the release notes for 18 May 2021.

Added information about working with environment variables in Code Engine.
: See [Working with environment variables](https://cloud.ibm.com/docs/codeengine?topic=codeengine-envvar).

Working with secrets and configmaps
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. 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).

Project limits
: Updated project limit information. See [Limits and quotas for project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).

Project deletions
: Updated information about project deletions and how these deletions can affect the maximum number of projects in a region. See [Delete a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-projectdelete-project).

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





 8 April 2021 

Review the release notes for 8 April 2021.

Learning paths
: Added curated Code Engine learning path information to help guide you from planning to working with your deployments. See [Learning paths for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-learning-paths).

Pending reclamation
* [Clean up for Object Storage tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cos-tutorialclean-subscription-cos)



[Subscribing to Kafka events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialsubscribe-kafka-tutorial)



* [Setting up the Kafka event producer](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-setup-sender)
* [Setting up a Code Engine sample app to produce Kafka messages](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-sender-app)
* [Setting up a Code Engine Kafka subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-subscribe-setup)
* [Testing your subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-test-subscription)
* [Updating your subscription](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-update-subscription)
* [Clean up for Kafka subscription tutorial](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialtutkafka-delete-subscription)
* [Next steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-kafka-tutorialnextsteps-kafkatut)
--case ${OFFLINEDIR}/ibm-cp-datacore-2.0.10.tgz 
--inventory cpdPlatformOperator 
--action configure-creds-airgap 
--args "--registry ${PRIVATE_REGISTRY} --user ${PRIVATE_REGISTRY_USER} --pass ${PRIVATE_REGISTRY_PASSWORD}"
8. Mirror the images:

export USE_SKOPEO=true
cloudctl case launch 
--case ${OFFLINEDIR}/ibm-cp-datacore-2.0.10.tgz 
--inventory cpdPlatformOperator 
--action mirror-images 
--args "--registry ${PRIVATE_REGISTRY} --user ${PRIVATE_REGISTRY_USER} --pass ${PRIVATE_REGISTRY_PASSWORD} --inputDir ${OFFLINEDIR}"
9. Create the Redis subscription.

a) Export the project that contains the IBM Cloud Pak® for Data operator:

export OPERATOR_NS=ibm-common-services|cpd-operators Select the project that contains the Cloud Pak for Data operator

b) Create the subscription:

cat <<EOF | oc apply --namespace $OPERATOR_NS -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
name: ibm-cloud-databases-redis-operator
spec:
name: ibm-cloud-databases-redis-operator
source: ibm-cloud-databases-redis-operator-catalog
sourceNamespace: openshift-marketplace
EOF







 IBM Entitled Registry 



1. Check the status of the Redis operator:

oc get opreq common-service-redis -n ibm-common-services -o jsonpath='{.status.phase} {"n"}'
2. If the Redis operand request is stuck in Pending status, delete the operand request:

oc delete opreq watson-assistant-redis -n ibm-common-services
3.
* [Subscribing to Periodic timer (cron) events for an application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-croneventing-cron-existing-app)



* [Subscribing to Periodic timer (cron) events for an application from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-croneventing-cron-existing-app-ui)
* [Subscribing to Periodic timer (cron) events for an application with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-croneventing-cron-existing-app-cli)
* [Updating your cron subscription with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronupdate-cron-sub-cli)
* [Viewing event information for an application from the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronview-eventing-cron-app-ui)
* [Viewing event information for an application with the CLI](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronview-eventing-cron-app-cli)
* [Cron header and body information for events delivered to applications](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-header-body-cron)



* [Subscribing to Periodic timer (cron) events for a job](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-croneventing-cron-job)
ibmcloud ac feature update-values --environment_id "production" --name "Indian IBMers" --feature_id "ibm-discount" --description "Discount given to IBM Indian employees" --enabled_value true --disabled_value false --segment_rules '[{"rules":{"segments":"ibm_employees"]}],"value": true,"order": 1}]' --tags "discount,sale"



 Output 

The command returns the following output:

updated_time 2021-02-02T18:06:03Z
description Discount given to IBM Indian employees
enabled_value true
disabled_value false
segment_rules <Array>
created_time 2021-02-02T17:52:46Z
name Indian IBMers
type BOOLEAN
collections <Array>









 ibmcloud ac feature delete 

You can delete a feature, by using the command:

ibmcloud ac feature delete --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID





 Example 

To delete a feature with ID ibm-discount, run the following command:

ibmcloud ac feature delete --environment_id "production" --feature_id ibm-discount



 Output 

The command returns the following output:

OK









 ibmcloud ac feature toggle 

You can toggle a feature value, by using the command:

ibmcloud ac feature toggle --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID --enabled ENABLED



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID

--enabled ENABLED
: The state of the feature flag.





 Example 

To toggle a feature value with ID ibm-discount, run the following command:

ibmcloud ac feature toggle --environment_id "production" --feature_id ibm-discount --enabled false



 Output 

The command returns the following output:
--file FILE
: Input through file. File format Supported - JSON





 Example 

To create a collection with name sample using flags ([click here](https://cloud.ibm.com/docs/app-configuration-cli-plugin?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac feature create --environment_id "production" --name "IBMers" --feature_id "ibm-discount" --description "Discount given to IBM employees" --type "BOOLEAN" --enabled_value true --disabled_value false --segment_rules '[{"rules":{"segments":"ibm_employees"]}],"value": true,"order": 1}]' --collections '[{"collection_id":"corporatediscount","enabled": true}]' --tags "discount,sale" --enabled true



 Output 

The command returns the following output:

type BOOLEAN
enabled_value true
segment_rules <Array>
collections <Array>
name IBMers
feature_id ibm-discount
description Discount given to IBM employees
disabled_value false
enabled true
created_time 2021-02-02T17:52:46Z
updated_time 2021-02-02T17:52:46Z









 ibmcloud ac feature get 

You can get a feature, by using the command:

ibmcloud ac feature get --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID [--include INCLUDE]



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID for the feature flag.

--include INCLUDE (optional)
: Include the associated collections in the response.





 Example 

To get a feature with ID ibm-discount, run the following command:

ibmcloud ac feature get --environment_id "production" --feature_id ibm-discount



 Output
You have attempted to create a new security group, but you are currently at your account quota. The quotas per resource are specified in [Quotas and limits for VPC](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotassecurity-groups-quotas). Evaluate your strategy for assigning instances to security groups. It is often possible to reduce the overall number of security groups by assigning multiple instances to the same security group. This strategy will reduce the number of security groups, and drop you below your account quota. In rare cases, generally for large organizations, there is a need for expanding the quota. In this case, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support) to inquire if this is possible.





 security_group_network_interface_not_active 

Message: The interface cannot be attached because it is not active.

Network interfaces must be active before attaching to security groups. Use GET /v1/instances/{id}/network_interfaces/{id}?version=$version&generation=1 or ibmcloud is instance-network-interface to view the status of an interface. Once the status is 'available', try again. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 security_group_not_attached 

Message: The interface is not attached.

The interface is not attached to the security group. Use GET /v1/security_groups/{id}/network_interfaces?version=$version&generation=1 or ibmcloud is security-group-network-interfaces to view attached interfaces.
--file FILE
: Input through the file. File format Supported - JSON





 Example 

To update description a feature with ID ibm-discount using flags ([click here](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-cli-plugin-app-configuration-cliac-fileinput) for using commands with '--file' flag), run the following command:

ibmcloud ac feature update-values --environment_id "production" --name "Indian IBMers" --feature_id "ibm-discount" --description "Discount given to IBM Indian employees" --enabled_value true --disabled_value false --segment_rules '[{"rules":{"segments":"ibm_employees"]}],"value": true,"order": 1}]' --tags "discount,sale"



 Output 

The command returns the following output:

updated_time 2021-02-02T18:06:03Z
description Discount given to IBM Indian employees
enabled_value true
disabled_value false
segment_rules <Array>
created_time 2021-02-02T17:52:46Z
name Indian IBMers
type BOOLEAN
collections <Array>









 ibmcloud ac feature delete 

You can delete a feature, by using the command:

ibmcloud ac feature delete --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID





 Example 

To delete a feature with ID ibm-discount, run the following command:

ibmcloud ac feature delete --environment_id "production" --feature_id ibm-discount



 Output 

The command returns the following output:

OK









 ibmcloud ac feature toggle 

You can toggle a feature value, by using the command:

ibmcloud ac feature toggle --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID --enabled ENABLED



 Command options 

--environment_id ENVIRONMENT_ID
The command returns the following output:

type BOOLEAN
enabled_value true
segment_rules <Array>
collections <Array>
name IBMers
feature_id ibm-discount
description Discount given to IBM employees
disabled_value false
enabled true
created_time 2021-02-02T17:52:46Z
updated_time 2021-02-02T17:52:46Z









 ibmcloud ac feature get 

You can get a feature, by using the command:

ibmcloud ac feature get --environment_id ENVIRONMENT_ID --feature_id FEATURE_ID [--include INCLUDE]



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--feature_id FEATURE_ID
: Feature ID for the feature flag.

--include INCLUDE (optional)
: Include the associated collections in the response.





 Example 

To get a feature with ID ibm-discount, run the following command:

ibmcloud ac feature get --environment_id "production" --feature_id ibm-discount



 Output 

The command returns the following output:

name type disabled_value updated_time feature_id description enabled_value created_time order rules value
IBMers BOOLEAN false 2021-02-02T17:52:46Z ibm-discount Discount given to IBM employees true 2021-02-02T17:52:46Z 1 <Array> true









 ibmcloud ac feature update 

You can update a feature, by using the command:

ibmcloud ac feature update {--file FILE-PATH | --environment_id ENVIRONMENT_ID --name NAME --feature_id FEATURE_ID --description DESCRIPTION --enabled_value ENABLED_VALUE --disabled_value DISABLED_VALUE --enabled ENABLED --tags TAGS --segment_rules SEGMENT_RULES --collections COLLECTIONS}



 Command options 

--environment_id ENVIRONMENT_ID
: Environment ID

--name NAME
: Feature name. Required field - input either as a flag or from file.

--feature_id FEATURE_ID
: Feature ID. Required field - input either as a flag or from file.

--description DESCRIPTION
Why does the Ingress status show an ESSVC error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The CRN does not match the default secret with the same domain (ESSVC).

  Why it’s happening 

There are secrets in multiple namespaces for the same domain in your cluster but they reference different IBM Cloud Secrets Manager CRNs.

  How to fix it 

Ensure all secrets that share the same domain have the same CRN.



1.  View all the Ingress secrets for your cluster by running the following command.

ibmcloud ks ingress secret ls
2.  In the output, ensure that secrets that have the same domain also have the same CRN. For secrets that have a different CRN, update them with the correct CRN by running the following command.

ibmcloud ks ingress secret update -c <cluster> --name <secret_name> --namespace <secret_namespace> --cert-crn <new_crn>

To find the correct CRN for the IBM Cloud Kubernetes Service managed domains look for the secret in the default, kube-system, or ibm-cert-store namespaces.
3.  If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Why does the Ingress status show an ESSVC error? 

Virtual Private Cloud

Classic infrastructure

Satellite

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following example.

The CRN does not match the default secret with the same domain (ESSVC).

  Why it’s happening 

There are secrets in multiple namespaces for the same domain in your cluster but they reference different IBM Cloud Secrets Manager CRNs.

  How to fix it 

Ensure all secrets that share the same domain have the same CRN.



1.  View all the Ingress secrets for your cluster by running the following command.

ibmcloud oc ingress secret ls
2.  In the output, ensure that secrets that have the same domain also have the same CRN. For secrets that have a different CRN, update them with the correct CRN by running the following command.

ibmcloud oc ingress secret update -c <cluster> --name <secret_name> --namespace <secret_namespace> --cert-crn <new_crn>

To find the correct CRN for the Red Hat OpenShift on IBM Cloud managed domains look for the secret in the openshift-ingress, or ibm-cert-store namespaces.
3.  If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Update Database Certificate and Edit Database connection 

To update the database certificate, complete the following steps in the Data Security Broker Manager:



1.  Click Databases from the left navigation and select a database.
2.  Click Update in the Database Summary pane on the right to update the Database Certificate.



If the credentials change for your database,
1 year Wallet tab: Click the ordering service admin identity tile to view the expiration date of the certificate and private key. <br> <br>MSP tab: Open the ordering service organization MSP tile and the admin certificate expiration date is listed in left column. [Enroll new identity](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-enroll) No action is required when Node OU is enabled for the MSP. <br> <br>Otherwise, [Append the admin certificate to the MSP definition](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-msp). No action is required when Node OU is enabled for the MSP. <br> <br>Otherwise, [Associate new admin identity on orderer](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-node-identity) No action is required when Node OU is enabled for the MSP. <br> <br>Otherwise, [Update ordering service admin](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-os-admin) <br> <br>or <br> <br>[Bulk admin certificate update with Ansible playbooks](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-bulk-ansible). All consortium members need to import the updated MSP into their Organizations tab. <br> <br>One consortium member needs to submit the request to [update the orderer member MSP on the application channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-cert-mgmtcert-mgmt-manual-update-channel). Transactions can continue to work successfully.
The following fields include extra information:



* The requestData.certificateId field indicates the target certificate.
* The responseData.action field indicates that the certificate is to be created or updated.







 List certificates by the certificate administrator 

The following field includes extra information:



* The responseData.action field indicates all certificates that are managed by current administrator are to be listed.







 Get certificates by the certificate administrator 

The following fields include extra information:



* The requestData.certificateId field indicates the target certificate.
* The responseData.action field indicates that the certificate is to be fetched and displayed.







 Remove certificates by the certificate administrator 

The following fields include extra information:



* The requestData.certificateId field indicates the target mTLS certificate.
* The responseData.action field indicates that the certificate is to be deleted.









 EP11 keystore events 

The following table lists the returned values that indicate a successful EP11 keystore event:



Table 15. Returned values of a successful EP11 keystore event

 Field name Returned value 

 outcome success 
 reason.reasonCode 200 
 reason.reasonType OK 



The following common fields for EP11 keystore events include extra information:



* The target.name field includes the IDs of the keystore or key.







 EP11 crypto events 

The following table lists the returned values that indicate a successful EP11 crypto event:



Table 16. Returned values of a successful EP11 crypto event

 Field name Returned value 

 outcome success 
 reason.reasonCode 200 
 reason.reasonType OK 









 Analyzing failed events 

All failed events contain the message field with detailed description of the problem.



 Lifecycle action on a key with registrations did not complete 

The responseData.reasonForFailure and responseData.resourceCRN fields contain information about why the action wasn't able to be completed.

If the event has a reason.reasonCode of 409, the action cannot be completed due to the adopting service's key state conflicting with the key state that Hyper Protect Crypto Services has.