vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Older revisions are not retained.

Listing all application revisions...
OK

Name Application Status URL Latest Tag Traffic Age Conditions Reason
myapp-hc3u8-2 myapp Ready 16d 3 OK / 4
myapp-hc3u8-3 myapp Ready true 100% 2d8h 3 OK / 4
newapp-mytest-00004 newapp-mytest Ready 4d20h 3 OK / 4
newapp-mytest-00005 newapp-mytest Ready true 100% 2d20h 3 OK / 4







 ibmcloud ce revision logs 

Display the logs of application revision instances.

ibmcloud ce revision logs (--instance REVISION_INSTANCE | --revision REVISION_NAME) [--all-containers] [--follow] [--output OUTPUT] [--quiet] [--tail TAIL] [--timestamps]



 Command Options 

--all-containers, --all
: Display the logs of all containers of the specified application revision instances. This value is optional. The default value is false.

--follow, -f
: Follow the logs of application revision instances. Use this option to stream logs of application revision instances. If you specify the --follow option, you must enter Ctrl+C to terminate this log command. This value is optional. The default value is false.

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

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--revision, --rev, -r, --name, -n
Instances:
Name Running Status Restarts Age
myjobrunresubmit-2-0 0/1 Succeeded 0 16s
myjobrunresubmit-3-0 0/1 Succeeded 0 16s
8. Display the job run logs of an instance of the myjobrunresubmit job run. This time, display the logs of the myjobrunresubmit-3-0 instance. The log displays Hello My little literal secret!, which is the value that is specified in the myliteralsecret2 secret. Use the jobrun get command to display the details of the job run, including the running instances of the job run.

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

Example output

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

myjobrunresubmit-3-0/myjob:
Hello from helloworld! I'm a batch job! Index: 3

Hello My little literal secret from:
. ___ __ ____ ____
./ __)/ ( ( __)
( (__( O )) D ( ) _)
.___)__/(____/(____)
.____ __ _ ___ __ __ _ ____
( __)( ( / __)( )( ( ( __)
.) _) / /( (_ )( / / ) _)
(____)_)__) ___/(__)_)__)(____)

Some Env Vars:
--------------
HOME=/root
HOSTNAME=myjobrunresubmit-3-0
JOB_INDEX=3
KUBERNETES_PORT=tcp://172.21.0.1:443
* [ibmcloud ce subscription kafka create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-create)
* [ibmcloud ce subscription kafka delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-delete)
* [ibmcloud ce subscription kafka get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-get)
* [ibmcloud ce subscription kafka list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-list)
* [ibmcloud ce subscription kafka update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-kafka-update)



* [Version command](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-version)



* [ibmcloud ce version](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-versioncmd)





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





 API reference 

[API reference](https://cloud.ibm.com/docs/codeengine?topic=codeengine-apiapi)



* [Retrieve your Kubernetes configuration with REST API](https://cloud.ibm.com/docs/codeengine?topic=codeengine-apiapi-rest)



* [Authenticate with Cloud Identity and Access Management](https://cloud.ibm.com/docs/codeengine?topic=codeengine-apiapi-iam)
Is streaming not working? 

Streaming is failing because your Log Analysis instance cannot connect to the Event Streams Kafka broker.

  What’s happening 

You get the following error message: Failed to connect to Kafka broker: KafkaJSSASLAuthenticationError: SASL PLAIN authentication failed: Authentication failed, invalid credentials.

  Why it’s happening 

The account has been configured to restrict access to configured IP address rules via IAM or the account limits the network locations that connections are accepted from.

  How to fix it 

Configure the account by allowlisting the Log Analysis CIDR blocks in the account. For more information, see [Log Analysis CIDR blocks](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cidr). Follow the instructions in [Event Streams - Restricting network access](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-restrict_access).
1. Verify that you set up service-to-service access. [Follow the steps](https://cloud.ibm.com/docs/codeengine?topic=codeengine-satellite-cesatellite-ce-authority) to set it up. Because Code Engine continuously polls Satellite for the assigned location, as soon as you set up service-to-service access, the compute environment creation process continues.
2. Verify that you added the env:codeengine label to your Satellite hosts.



1. Go to [Satellite location](https://cloud.ibm.com/satellite/locations).
2. Select the Satellite location that you want to use for your compute environment.
3. Click Hosts.
4. Look at the labels field for the hosts that you want to use for Code Engine. If they do not have the env:codeengine label, then [follow the instructions](https://cloud.ibm.com/docs/satellite?topic=satellite-assigning-hostshost-autoassign-ov) to add host labels.









 Why can't I access my app? 

Your Code Engine app uses the primary network interfaces from your Satellite hosts. If the IP addresses for these interfaces are not publicly accessible, then your app is available only from the private network.

To find the IP address that your application uses, follow these steps.



1. Find the domain for your application on the Application details page. Look for the Public URL field under Endpoints.
2. Use a DNS lookup tool (for example, dig or nslookup) to find the IP addresses used by this domain. For example,

dig myapp-abcdefg.ce-abc1abcd23efghijklmn-4o5ddc1a6fde0ec0aebe4cf134f8c000-0000.eu-de.containers.appdomain.cloud A +short

The dig command returns information similar to the following example. Your IP addresses are different, depending on the domain that your app is assigned.

10.0.2.244
ibmcloud ce sub kafka create --name mykafkasubscription --destination kafka-receiver-app --secret kafka-subscription-secret --topic kafka-topic1 --broker broker-3-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-5-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-0-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-1-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-4-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-2-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093
4. Display the details of the Kafka event subscription.

ibmcloud ce sub kafka get -n mykafkasubscription

Example output

Getting Kafka event subscription 'mykafkasubscription'...
OK

Name: mykafkasubscription
[...]
Destination Type: app
Destination: kafka-receiver-app
Brokers:
broker-3-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093
broker-5-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093
}
Show more

Example registration payload (for reference only):


{ "token_endpoint_auth_method":"client_secret_basic", "client_id": "N3NzNVFsSjlLVkl6Zk5hZ01MRzJVaVdnbFcxNGl5cnQK", "client_secret": "VWNVNzF4ZUxNSVBQUHZHdG1xQmNsTTFOWmNUUGlnYUkK", "scope":"openid profile email", "grant_types":[ "authorization_code", "client_credentials", "password", "implicit", "refresh_token", "urn:ietf:params:oauth:grant-type:jwt-bearer" ], "response_types":[ "code", "token", "id_token token" ], "application_type":"web", "subject_type":"public", "post_logout_redirect_uris":[" [https://icp-console.apps.test.ibm.com](https://icp-console.apps.test.ibm.com)"], "preauthorized_scope":"openid profile email general", "introspect_tokens":true, "trusted_uri_prefixes":[" [https://icp-console.apps.test.ibm.com/](https://icp-console.apps.test.ibm.com/)"], "redirect_uris":[" [https://icp-console.apps.test.ibm.com/auth/liberty/callback","https://www.cf-dev.test.ibm.com/oidc_login/redirect_uri](https://icp-console.apps.test.ibm.com/auth/liberty/callback%22,%22https://www.cf-dev.test.ibm.com/oidc_login/redirect_uri)"] }

1.
You need to save the "enrollid" and "enrollsecret" from the command above for when you create your configuration file.<-- </section "id="section-ibp-v2-apis-config-register-component-tls" "> --><-- <section "id="section-ibp-v2-apis-config-troubleshooting" "> --> Troubleshooting <-- <section "id="section-ibp-v2-apis-config-enroll-error1" "> --> Problem: Error when running the enroll command When running the Fabric CA client enroll command, it is possible the command fails with the following error: Error: Failed to read config file at '/Users/chandra/fabric-ca-client/ca-admin/fabric-ca-client-config.yaml': While parsing config: yaml: line 42: mapping values are not allowed in this context
Solution:This error can occur when your Fabric CA client tries to enroll but cannot connect to your CA. This can happen if:<-- <ul> --> * Your enroll command contains an extra https:// on the -u parameter. * Your CA name is incorrect. * Your username or password is incorrect.<-- </ul> -->Review the parameters that you specified on your enroll command and ensure that none of these conditions exist.<-- </section "id="section-ibp-v2-apis-config-enroll-error1" "> --><-- <section "id="section-ibp-v2-apis-config-enroll-error2" "> --> Problem: Error with CA URL when running the enroll command The Fabric CA client enroll command can fail if the enrollment URL, the -u parameter value, contains a special character.
Use the kafka-subscription-secret secret that you previously created to access the message broker. Specify the broker information based on the service credentials information for your Kafka resource. For this example, you can obtain the broker information from the output of the ibmcloud resource service-key myeventstream-key command. Notice that you must specify a --broker option for each broker for your topic. The --destination option specifies the Code Engine resource that receives the events.

ibmcloud ce sub kafka create --name mykafkasubscription --destination kafka-receiver-app --secret kafka-subscription-secret --topic kafka-topic1 --broker broker-3-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-5-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-0-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-1-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-4-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093 --broker broker-2-abcdabcdabcdabcd.kafka.svc07.us-south.eventstreams.cloud.ibm.com:9093
4. Display the details of the Kafka event subscription.

ibmcloud ce sub kafka get -n mykafkasubscription

Example output

Getting Kafka event subscription 'mykafkasubscription'...
OK

Name: mykafkasubscription
[...]
Destination Type: app
Destination: kafka-receiver-app
* [ibmcloud ce secret get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret-get)
* [ibmcloud ce secret list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret-list)
* [ibmcloud ce secret update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-secret-update)



* [Subscription cos commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos)



* [ibmcloud ce subscription cos create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-create)
* [ibmcloud ce subscription cos delete](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-delete)
* [ibmcloud ce subscription cos get](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-get)
* [ibmcloud ce subscription cos list](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-list)
* [ibmcloud ce subscription cos update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cos-update)



* [Subscription cron commands](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron)



* [ibmcloud ce subscription cron create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-subscription-cron-create)
{"firefox": { <br>"name": "Firefox", <br>"pref_url": "about:config" <br>}} STRING JSON map[string]interface{} map[browsers:mapfirefox:mapname:Firefox pref_url:about:config]]] 
 men: <br>- John Smith <br>- Bill Jones <br>women: <br>- Mary Smith <br>- Susan Williams STRING YAML map[string]interface{} map[men:John Smith Bill Jones] women:Mary Smith Susan Williams]] 





 Feature flag 

feature, err := appConfigClient.GetFeature("json-feature")
if err == nil {
feature.GetFeatureDataType() // STRING
feature.GetFeatureDataFormat() // JSON

// Example (traversing the returned map)
result := feature.GetCurrentValue(entityID, entityAttributes) // JSON value is returned as a Map
result.(map[string]interface{})["key"] // returns the value of the key
}

feature, err := appConfigClient.GetFeature("yaml-feature")
if err == nil {
feature.GetFeatureDataType() // STRING
feature.GetFeatureDataFormat() // YAML

// Example (traversing the returned map)
result := feature.GetCurrentValue(entityID, entityAttributes) // YAML value is returned as a Map
result.(map[string]interface{})["key"] // returns the value of the key
}
Show more



 Property 

property, err := appConfigClient.GetProperty("json-property")
if err == nil {
property.GetPropertyDataType() // STRING
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:

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 segment list 

You can list all segments, by using the command:

ibmcloud ac segment list [--limit LIMIT] [--offset OFFSET] [--sort SORT] [--tags TAGS] [--expand EXPAND] [--include INCLUDE]



 Command options 

--limit LIMIT (optional)
: Used for pagination. The number of records to retrieve.

--include INCLUDE (optional)
: Segment details to include the associated rules in the response.

--offset OFFSET (optional)
: Used for pagination. The number of records to skip.

--expand EXPAND (optional)
: Expanded view the segment details.

--tags TAGS (optional)
: Filter segments by a list of comma-separated tags.

--sort SORT (optional)
: Sort the details based on the specified attribute.





 Example 

To list all segments, run the following command:

ibmcloud ac segment list



 Output
Retrieving and modifying attributes for keys 

When you generate keys or perform key operations, you define an attribute template as one of the parameters. You can retrieve the attributes for a specific key object and modify some attributes after the key is created.



 GetAttributeValue 

The GetAttributeValue function obtains an attribute value of an object.

Enterprise PKCS #11 over gRPC

Enterprise PKCS #11

PKCS #11





 Description Binds to EP11 m_GetAttributeValue, which is an implementation of PKCS #11 C_GetAttributeValue. 
 Parameters message GetAttributeValueRequest { bytes Object = 1; map<uint64,AttributeValue> Attributes = 3; } message GetAttributeValueResponse { map<uint64,AttributeValue> Attributes = 4; } 
 Return values Wraps EP11 error into message Grep11Error. 



Code snippets



* Golang code snippet

// Only retrieve supported EP11 attributes
attributeList := ep11.EP11Attributes{
ep11.CKA_DECRYPT: false, // attribute where you would like to retrieve its current value
}

GetAttributeValueRequest := &pb.GetAttributeValueRequest{
Object: GenerateKeyPairResponse.PrivKeyBytes,
Attributes: util.AttributeMap(attributeList),
}

GetAttributeValueResponse, err := cryptoClient.GetAttributeValue(context.Background(), GetAttributeValueRequest)
* JavaScript code snippet

const attributeTemplate = new util.AttributeMap(
new util.Attribute(ep11.CKA_SIGN, 0)
);

client.GetAttributeValue({
Object: keys.PrivKey,
Attributes: attributeTemplate
}, (err, response) => {
callback(err, response);
userProfileManager.getAllAttributes(accessToken).then(function (attributes) {

});

// get single attribute
userProfileManager.getAttribute(accessToken, name).then(function (attributes) {

});

// set attribute value
userProfileManager.setAttribute(accessToken, name, value).then(function (attributes) {

});

// delete attribute
userProfileManager.deleteAttribute(accessToken, name).then(function () {

});

//iOS Swift example

func setAttribute(key: String, value: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)
func setAttribute(key: String, value: String, accessTokenString: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)

func getAttribute(key: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)
func getAttribute(key: String, accessTokenString: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)

func getAttributes(completionHandler: @escaping(Error?, [String:Any]?) -> Void)
func getAttributes(accessTokenString: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)

func deleteAttribute(key: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)
func deleteAttribute(key: String, accessTokenString: String, completionHandler: @escaping(Error?, [String:Any]?) -> Void)

//Server-side Swift example
error: failed to solve: failed to read dockerfile: open /tmp/buildkit-mount306846082/Dockerfile: no such file or directory Dockerfile <br><br> * The Dockerfile is not in the root directory of the source repository.<br> * The source repository does not contain a Dockerfile at all.<br><br><br> 
 error: failed to solve: unexpected status: 403 Forbidden <br>DENIED: You have exceeded your storage quota. Delete one or more images, or review your storage quota and pricing plan. For more information, see https://ibm.biz/BdjFwL Dockerfile, Buildpacks <br><br> * IBM Cloud® Container Registry is used and a quota limit is reached.<br><br><br> 
 ERROR: No buildpack groups passed detection. Buildpacks <br><br> * The source of the build was not specified correctly. The typical reason for this error is that the sources are not in the root directory of the Git repository, but rather in a child directory.<br> * Buildpacks is not supported to build the sources.<br><br><br> 
 429 Too Many Requests - Server message: toomanyrequests: You have reached your pull rate limit. Dockerfile <br><br> * The Dockerfile pull rate limit is reached.<br><br><br> 
 Any other error message Dockerfile, Buildpacks <br><br> * There's a problem with the Docker build.<br> * There's a problem with the source code.<br><br><br> 



 How to fix it 

Try using the following information to resolve your problem.

Whether you are running your build in the console or in the CLI, use the CLI for troubleshooting problems with your build.



1. Run the ibmcloud ce buildrun get --name BUILDRUN_NAME command to display the details of your build run.
2. Review the Reason in the command output.
If the updated access permissions do not resolve the issue, verify with the account owner that the [Restrict API key creation](https://cloud.ibm.com/docs/account?topic=account-allow-api-create) and [Restrict service ID creation](https://cloud.ibm.com/docs/account?topic=account-restrict-service-id-create) options are disabled on the account.

Zoom

![The figure shows a simplified IAM dashboard with numbered steps for disabling account restrictions.](https://cloud.ibm.com/docs-content/v1/content/991f60ddbe3ab0a9aa69481a07a0a73b359fa329/secrets-manager/images/disable-acct-restrictions.svg)

Figure 1. Disabling API key and service ID restrictions

If the problem persists, contact IBM Cloud support.
Generate an API key, then request a refresh token. For more information, see [Generating an IBM Cloud IAM token by using an API key](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).
2. Copy one of the following example requests and replace the variables that you want to use.

Example request to create a version 1.0.4 configuration.

curl -X POST "https://containers.cloud.ibm.com/global/v2/storage/satellite/createStorageConfigurationByController" -H "accept: application/json" -H "Authorization: TOKEN" -H "Content-Type: application/json" -d "{ "config-name": "string", "controller": "string", "storage-class-parameters": [ { "additionalProp1": "string", "additionalProp2": "string", "additionalProp3": "string" } ], "storage-template-name": "gcp-compute-persistent-disk-csi-driver", "storage-template-version": "1.0.4", "update-assignments": true, "user-config-parameters":"user-secret-parameters": { "entry.name": "PROJECT_ID",{ "entry.name": "PRIVATE_KEY_ID",{ "entry.name": "PRIVATE_KEY",{ "entry.name": "CLIENT_EMAIL",{ "entry.name": "CLIENT_ID",{ "entry.name": "AUTH_URI",{ "entry.name": "TOKEN_URI",{ "entry.name": "AUTH_PROVIDER_X509_CERT_URL",{ "entry.name": "CLIENT_X509_CERT_URL",}

Example request to create a version 1.7.1 configuration.
ibmcloud resource service-instance-create example-upgrade messages-for-rabbitmq standard us-south -p '{"backup_id": "crn:v1:bluemix:public:messages-for-rabbitmq:us-south:a/54e8ffe85dcedf470db5b5ee6ac4a8d8:1b8f53db-fc2d-4e24-8470-f82b15c71717:backup:06392e97-df90-46d8-98e8-cb67e9e0a8e6", "version":3.8}'





 Upgrading through the API 

Similar to provisioning through the API, you need to complete [the necessary steps to use the resource controller API](https://cloud.ibm.com/docs/databases-for-postgresql?topic=cloud-databases-provisioningprovisioning-through-the-resource-controller-api) before you can use it to upgrade from a backup. Then, send the API a POST request. The parameters name, target, resource_group, and resource_plan_id are all required. You also supply the version and backup ID. If you need to use a key protect key, resize the deployment, or allocate dedicated cores, you can do so with the optional parameters key_protect_key, members_disk_allocation_mb, members_memory_allocation_mb, or members_cpu_allocation_count, along with their respective values to the body of the request.

curl -X POST https://resource-controller.bluemix.net/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "my-instance",
"target": "bluemix-us-south",
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "messages-for-rabbitmq-standard",