vania-janet/multiturn-rag-retrieval-data huggingface dataset:
However, the operator secret might not contain the necessary information about the service ID so that details about the service binding configuration cannot be displayed from the Integrations page for project-wide settings.

The operator secret that was created because one of the following scenarios might not have the service ID information.



1. If the [project update](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-project-update) CLI command was run with the --binding-service-id option.
2. If you created service bindings from the console or with the CLI for a Code Engine app or job in a project that was created before the release of [project-wide settings in the console](https://cloud.ibm.com/docs/codeengine?topic=codeengine-codeengine-relnotescodeengine-apr2623), the operator secret does not reference the service ID. Note that for projects that were created after the release of project-wide settings in the console, the operator secret contains information about the service ID. Code Engine uses this information to display details about the service binding operations, including information about the operator secret and the service ID.



 How to fix it 

Try one of these solutions.



1. If you used a custom service ID that you created and manage with the project update command, and you know the specific service ID that was used, take the following steps to reconfigure the service binding operations to use your custom service ID.

If you do not know the specific service ID that was used with the project update command, do not take the following steps. For this case, service binding operations are configured such that you can create and manage service bindings; however, the system cannot display details of service binding operations from the project-wide Integrations page and you continue to see the warning message.



1. Review the list of service IDs in IBM Cloud® Identity and Access Management (IAM) to help you determine the custom service ID that was used with the project update command. From the IBM Cloud console, go to Manage > Access (IAM), and select Service IDs.
2.
For example, if one slot captures a product ID (@id) with a syntax like GR1234 and another slot captures a number (@number), such as 1234, then user input that contains an ID, such as BR3344 might get claimed by the @number slot as a number reference and fill the $number context variable with 3344.

Solution: Place the slot with the entity condition that captures the longer pattern (@id) higher in the list of slots than the condition that captures the shorter pattern (@number).
* Problem: A term is recognized as more than one system entity type.

For example, if the user enters May 2, then your assistant recognizes both the @sys-date (2017-05-02) and @sys-number (2) entities.

Solution: In logic that is unique to the slots feature, when two system entities are recognized in a single user input, the one with the larger span is used. Therefore, even though your assistant recognizes both system entities in the text, only the system entity with the longer span (@sys-date with 2017-05-02) is registered and applied to the slot.

This workaround is not necessary if you are using the revised system entities. With the updated entities, a date reference is considered to be a @sys-date mention only, and is not also treated as a @sys-number mention. For more details, see [System entities](https://cloud.ibm.com/docs/assistant?topic=assistant-system-entities).







 Adding conditions to Found and Not found responses 

For each slot, you can use conditional responses with associated actions to help you extract the information you need from the user. To do so, follow these steps:



1. Click the Customize slot![Customize slot](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/edit-slot.png) icon for the slot to which you want to add conditional Found and Not found responses.
2. From the More!
From the response section of the node, click the More![More options](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/kabob.png) icon, and then select Open context editor.

![Shows the Open context editor menu option from the node edit view.](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/gs-ass-open-context-editor.png)
6. Enter the following context variable name and value pair:



Order number context variable details

 Variable Value 

 $ordernumber 



The context variable value (<? @order_number.literal ?>) is a SpEL expression that captures the number that the user specifies that matches the pattern defined by the @order_number pattern entity. It saves it to the $ordernumber variable.

![Shows the $ordernumber context variable definition.](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/gs-ass-ordernumber-context-var.png)
7. Click ![Close](https://cloud.ibm.com/docs-content/v1/content/a2b18c153837bce00a5b4de496e4b4ca64bbf56e/assistant-data/images/close.png) to close the edit view.

Now, add child nodes that either ask for the order number or get confirmation from the user that she wants to cancel an order with the detected order number.
8. Click the More!
appconfig_client.set_context(collection_id='collection_id', environment_id='environment_id', options={
'bootstrap_file': 'saflights/flights.json',
'live_config_update_enabled': False
})

Where:



* bootstrap_file: Absolute path of the JSON file, which contains configuration details. Make sure to provide a proper JSON file. You can generate this file by using ibmcloud ac config command of the IBM Cloud App Configuration CLI.
* live_config_update_enabled: Live configuration update from the server. Set this value to False if the new configuration values must not be fetched from the server. By default, this value is set to True.







 Examples for using feature and property-related APIs 

Refer to the listed examples for using the feature and property-related APIs.



 Get single feature 

feature = appconfig_client.get_feature('online-check-in') feature can be None incase of an invalid feature id

if feature is not None:
print(f'Feature Name : {0}'.format(feature.get_feature_name()))
print(f'Feature Id : {0}'.format(feature.get_feature_id()))
print(f'Feature Data Type : {0}'.format(feature.get_feature_data_type()))
if feature.is_enabled():
 feature flag is enabled
else:
 feature flag is disabled





 Get all features 

features_dictionary = appconfig_client.get_features()





 Feature evaluation 

You can use the feature.get_current_value(entity_id, entity_attributes) method to evaluate the value of the feature flag. This method returns one of the Enabled or Disabled or Overridden value based on the evaluation. The data type of returned value matches that of feature flag.

entity_id = "john_doe"
entity_attributes = {
'city': 'Bangalore',
'country': 'India'
"vpcId": "<SUBNET_ID>",
"vmType": "cx2-2x4",
"securityGroupIds": "<SECURITY_GROUP_ID>"],
"sshkey_id": "<SSH_KEY_ID>",
"region": "us-south",
"zone": "us-south-1",
"userData": "<TemplateID>"
}
]
}



Please use a valid value for Template ID. A '-' (hypen) cant be used in templateId when using it as a string resource. User may see this error: Error in select section: Operator "-" cannot be used with type , to get type . Job not submitted.



2. When the template is added, you can use the lsf.shared file to map the new template to a specific job. The lsf.shared file is located in $LSF_ENVDIR (same location as lsf.conf). In a typical installation, this would be found in the /opt/ibm/lsf/conf folder. Add templateId as a resource in the resource section in the lsf.shared file. For example, templateID String () () (template ID for the external hosts).
3. Add the following section to user_data.sh to let the virtual machines add templateId as LSF_LOCAL_RESOURCES.

if [ -n "$template_id" ]; then
sed -i "s/(LSF_LOCAL_RESOURCES=.)"/1 [resourcemap $template_idtemplateID]"/" $LSF_CONF_FILE
echo "update LSF_LOCAL_RESOURCES in $LSF_CONF_FILE successfully, add [resourcemap ${template_id}templateID]" >> $logfile
else
echo "templateID doesn't exist in environment variable" >> $logfile
fi
* Resources: The resource group of this Code Engine project
* Resource group access:Viewer
* Roles and actions:Writer service access and Operator platform access





For Code Engine to automatically generate a service ID for service binding operations, Code Engine checks and automatically sets up a service ID with Operator platform access and Manager service access for all services in the resource group of the Code Engine project. Code Engine uses this service ID to access IBM Cloud services with service bindings.

If you use your own custom service ID, the custom service ID must provide Operator platform access and Manager service access for any IBM Cloud services or service instances that you want to bind to Code Engine apps or jobs.

If this service ID does not exist, Code Engine tries to automatically create this service ID whenever a service binding is created. The successful creation of this service ID for service binding operations depends on whether the user that is logged in to Code Engine has sufficient permissions. If the operator secret is not created successfully, any attempt to create a service binding fails. For more information about Code Engine access requirements for service binding operations, see [Configuring access for service bindings](https://cloud.ibm.com/docs/codeengine?topic=codeengine-configure-bindaccess).





 What's the relationship between the service ID and the operator secret? 

When you configure service binding operations, you can view details about what Code Engine does for you, including information about the service ID, API key, and secret.

In Code Engine, a service binding is the relationship between an app or job and another IBM Cloud service.

Code Engine uses a service ID to perform binding operations on behalf of the user, instead of using the identity of the user that is logged in. The service ID creates credentials for a specific IBM Cloud service instance. These service credentials are used by your bound Code Engine apps and jobs to interact with the service instances. The API key for the service ID is stored in the operator secret. The access policies are the permissions that are given to the service ID.

The operator secret or ibmcloud-operator-secret is a Code Engine generated and managed secret that includes the service ID and an autogenerated API key for it.
To add one or more words to a custom model at one time, use the POST /v1/customizations/{customization_id}/words method. You specify the entries to be added to the custom model as a JSON array of word/translation pairs. The required Content-Type header identifies the type of the input as application-json.

The following example adds common sounds-like translations for the words NCAA and iPhone to a custom model:

IBM Cloud

curl -X POST -u "apikey:{apikey}" --header "Content-Type: application/json" --data "{"words": [{"word":"NCAA", "translation":"N C double A"}, {"word":"iPhone", "translation":"I phone"}]}" "{url}/v1/customizations/{customization_id}/words"

IBM Cloud Pak for Data

curl -X POST --header "Authorization: Bearer {token}" --header "Content-Type: application/json" --data "{"words": [{"word":"NCAA", "translation":"N C double A"}, {"word":"iPhone", "translation":"I phone"}]}" "{url}/v1/customizations/{customization_id}/words"

The JSON content sent in the request body equates to the following:

{
"words": [
{"word":"NCAA", "translation":"N C double A"},
{"word":"iPhone", "translation":"I phone"}
]
}

As mentioned in [Updating a custom model](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-customModelscuModelsUpdate), you can also use the POST /v1/customizations/{customization_id} method to add words to a custom model. The following example uses this method to add the same two words as the previous example; it makes no changes to the model's metadata.
<-- <section "id="section-update-waf-group-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.WAF_PACKAGE_ID: The ID of WAF package. Required.WAF_GROUP_ID: The ID of WAF group. Required.WAF_GROUP_MODE: The mode of WAF group. Valid values are: on, off. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-waf-group-options" "> --><-- <section "id="section-update-waf-group-examples" "> --> Examples Enable WAF group de677e5818985db1285d0e80225f06e5 in WAF package a25a9a7e9c00afc1fb2e0245519d725b. ibmcloud cis waf-group-mode-set 31984fea73a15b45779fa0df4ef62f9b a25a9a7e9c00afc1fb2e0245519d725b de677e5818985db1285d0e80225f06e5 on -i "cis-demo"
<-- </section "id="section-update-waf-group-examples" "> --><-- </section "id="section-update-waf-group" "> --><-- <section "id="section-list-waf-rules" "> --> ibmcloud cis waf-rules List all WAF rules of a WAF package. ibmcloud cis waf-rules DNS_DOMAIN_ID WAF_PACKAGE_ID --page PAGE] --per-page NUM] -i, --instance INSTANCE] --output FORMAT] ! ! ! !
[Custom](https://cloud.ibm.com/docs/appid?topic=appid-custom-auth) Already have your own custom flow? No problem. You can use the custom identity flow to integrate App ID with your app. 
 [Anonymous](https://cloud.ibm.com/docs/appid?topic=appid-anonymous) With App ID, you can begin tracking a users activity before their initial sign-in to your app by using anonymous authentication. 
 [Ingress](https://cloud.ibm.com/docs/appid?topic=appid-kube-auth) With App ID, you can consistently enforce policy-driven security by using the Ingress networking capability in IBM Cloud Kubernetes Service. 
 [Istio](https://cloud.ibm.com/docs/appid?topic=appid-istio-adapter) By using the App Identity and Access adapter, you can centralize all your identity management in a single place. Because enterprises use clouds from multiple providers or a combination of on and off-premise solutions, heterogeneous deployment models can help you to preserve existing infrastructure and avoid vendor lock-in.
ibmcloud workload-protection compliance task run --id ID (--instance-id INSTANCE_ID | --instance-name INSTANCE_NAME) [--region REGION] [--output FORMAT] [--quiet]



 Compliance task run command options 

--id ID
: The task ID of the compliance task. You can find a list of configured tasks by running the [ibmcloud workload-protection compliance tasks command.](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-workload-protection-compliance-cliss_compliance_tasklist)

See the [command options](https://cloud.ibm.com/docs/workload-protection?topic=workload-protection-workload-protection-compliance-cliss_compliance_options) for a description of additional options.
curl -X PUT -u "apikey:{apikey}" --header "Content-Type: application/json" --data "{"sounds_like": ["I. B. M."], "display_as":"IBM™"}" "{url}/v1/customizations/{customization_id}/words/IBM"

IBM Cloud Pak for Data

curl -X PUT --header "Authorization: Bearer {token}" --header "Content-Type: application/json" --data "{"sounds_like": ["I. B. M."], "display_as":"IBM™"}" "{url}/v1/customizations/{customization_id}/words/IBM"



 Interaction with smart formatting and numeric redaction 

If you use the smart_formatting or redaction parameters with a recognition request, be aware that the service applies smart formatting and redaction to a word before it considers the display_as field for the word. You might need to experiment with results to ensure that the features do not interfere with how your custom words are displayed. You might also need to add custom words to accommodate the effects.

For instance, suppose that you add the custom word one with a display_as field of one. Smart formatting changes the word one to the number 1, and the display-as value is not applied. To work around this issue, you could add a custom word for the number 1 and apply the same display_as field to that word.

For more information about working with these features, see [Smart formatting](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-formattingsmart-formatting) and [Numeric redaction](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-formattingnumeric-redaction).







 What happens when I add or modify a custom word? 

How the service responds to a request to add or modify a custom word depends on the fields and values that you specify.
This service ID must have the Operator role and an appropriate service role for one or more service instances, service types, or resource groups. 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.





 Example 

ibmcloud ce project update --binding-service-id ServiceId-1234abcd-abcd-abcd-1111-1a2b3c4d5e6f





 Example output 

Configuring your project for service bindings...
Creating service binding API key 'my-project-api-key' for service ID 'my-custom-service-id'...
OK









 Reclamation commands 

Manage Code Engine project reclamations. Projects that are soft-deleted can be restored within 7 days by using the reclamation restore command.



 ibmcloud ce reclamation delete 

Delete a project reclamation.

ibmcloud ce reclamation delete (--name PROJECT_NAME | --id PROJECT_ID) [--force] [--no-wait] [--quiet] [--wait] [--wait-timeout WAIT_TIMEOUT]



 Command Options 

--force, -f
: Force deletion without confirmation. This value is optional. The default value is false.

--id, --guid
: The ID of the project. This value is required if --name is not specified.

--name, -n
: The name of the project. This value is required if --id is not specified.

--no-wait, --nw
: Delete the project reclamation and do not wait for the project reclamation to be deleted. If you specify the no-wait option, the project reclamation delete begins and does not wait. Use the reclamation get command to check the project reclamation status. This value is optional. The default value is false.

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

--wait, -w
By default, custom attributes are modifiable and can be updated by using an App ID access token from a client application. Without taking proper precautions, either the user or the application can update custom attributes immediately following the first user sign-in, if they have an access token. Doing so can potentially lead to unintended consequences. For example, a user might change their role from user to admin, which might expose administrative privileges to malicious users.



1. Go to the User profiles > Settings tab of the App ID dashboard.
2. Toggle custom attributes to Enabled.
3. Obtain access and identity tokens with the API.



1. Obtain your tenant ID, client ID, secret, and OAuth Server URL from your credentials.
2. Encode your client ID and secret by using a base64 encoder.
3. Use the following code examples to retrieve your tokens. The grant type that you use to obtain your token can differ depending on the type of authorization that you're working with. For a detailed list of options, check out the [swagger documentation](https://us-south.appid.cloud.ibm.com/swagger-ui//Authorization%20Server%20-%20Authorization%20Server%20V4/oauth-server.token).



* Curl
* Java
* Node
* Swift
* Swift



curl -X POST 'https://<region>.appid.cloud.ibm.com/oauth/v4/<tenantID>/token' -H 'Authorization: Basic base64Encoded{<clientID>:<clientSecret>}' -H 'Accept: application/json' -F 'grant_type=password' -F 'username=testuser@test.com' -F 'password=testuser'

AppID.getInstance().signinWithResourceOwnerPassword(getApplicationContext(), username, password, new TokenResponseListener() {
@Override
public void onAuthorizationFailure (AuthorizationException exception) {
//Exception occurred
"id" : "1123ed42-4356-efa1-1101-235900fe9087",
"created_at" : "2023-02-22T19:51:23.253Z",
"definition" : {
"description" : "a project example",
"name" : "iaas-infra-stage-env",
"destroy_on_delete" : false
},
"crn" : "crn:v1:staging:public:project:eu-de:a/06580d923e40314421d3b6cb40c01c68:cfbf9050-ab8e-ac97-b01b-ab5af830be8a::",
"location" : "eu-gb",
"resource_group" : "Default",
"state" : "UPDATING",
"cumulative_needs_attention_view" : ]
} ] ! ! ! !
}
<-- </section "id="section-project-list-cli-output" "> --><-- </section "id="section-project-cli-list-command" "> --><-- <section "id="section-project-cli-get-command" "> --> ibmcloud project get Get information about a project. ibmcloud project get --id ID
<-- <section "id="section-project-get-cli-options" "> --> Command options --id (string): The unique project ID. Required.
The maximum length is 128 characters. The value must match regular expression /^\.\-0-9a-zA-Z] ! ! ! ! +$/.
<-- </section "id="section-project-get-cli-options" "> --><-- <section "id="section-project-get-examples" "> --> Example ibmcloud project get --id=exampleString
: You can enhance the appearance of your private catalog to match your brand by adding a custom banner image to your private catalogs. For more information about personalizing your private catalog, see [Branding your private catalog with a custom banner](https://cloud.ibm.com/docs/account?topic=account-restrict-by-usercustomer-banner).

Add a custom provider name for your private products
: You can make it easier for users to search for your products added to a private catalog by specifying a custom provider name. Adding a custom provider name for your private products can help users find them quickly by using the Provider filter in the catalog. For more information, see [Providing catalog entry details](https://cloud.ibm.com/docs/account?topic=account-cm-catalog-detailscm-catalog-entry).







 March 2023 



 29 March 2023 

Generate a report on the MFA status of account users
: Users that don't meet MFA requirements leave your account vulnerable. You can now identify the users in your account that don't satisfy your MFA requirements. For more information, see [Identifying a user's MFA status](https://cloud.ibm.com/docs/account?topic=account-id-user-mfa).

An extra layer of security for users that don't use MFA
: IBM Cloud recommends enabling multifactor authentication (MFA) for all users in your account, but some automation scenarios might require you to exclude specific users from your MFA requirement. For users that are excluded from MFA, you can make access more secure by disabling CLI logins with only a username and password. This way, you require an API key to log in to the CLI or users can log in with --sso. For more information, see [Disabling MFA](https://cloud.ibm.com/docs/account?topic=account-enablemfadisablemfa).







 February 2023 



 22 February 2023 

User-specific MFA
: You can now enforce user-specific multifactor authentication (MFA) requirements that differ from the account default MFA setting.