vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Before you create an App Configuration tool integration in your toolchain, make sure that you provision an instance of the App Configuration service in a region and resource group that your toolchain can refer to.



1. If you are configuring this tool integration as you are creating the toolchain, and an App Configuration tool integration exists within the template that you are configuring, click the App Configuration tab. Alternatively, in the More tools section, click App Configuration.
2. If you have an existing toolchain and are adding this tool integration to it, from the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg) and select DevOps. On the Toolchains page, click the existing toolchain to open its Overview page. Alternatively, on your app's Overview page, on the Continuous delivery card, click View toolchain. Then, click Overview.

a. Click Add tool.

b. In the Tool Integrations section, click App Configuration.
3. Type the name that you want to display for this new tool integration on the App Configuration card in your toolchain. This name is used to identify the tool integration in your toolchain.
4. Select the Region and Resource group where your App Configuration service instance exists.
5. Select the appropriate App Configuration Environment and App Configuration Collection options from your chosen App Configuration service instance.
6. Click Create Integration.







 Applying feature flags and properties 

After you configure your App Configuration tool integration, you can use it to apply feature flags and properties to the toolchain environment and trigger properties.



1. Within the Pipeline environment properties tab or the Trigger properties tab, click Add to display the list of available property types.
2. Select AppConfig value and choose the feature flags or properties that you want to apply to the toolchain environment and trigger properties.
3.
Use cases <br><br> * Set up an end-to-end platform to collect, organize, and analyze your data.<br> * Create interactive data visualizations and analyze information for insights across data sets, without needing to code.<br> * Operationalize your data with AI and a suite of governance tools to make sure that your data is curated, useful, trusted, and ready for analysis.<br><br><br> 
 [Catalog entry](https://cloud.ibm.com/catalog?search=label%3Acloud_pak) For included components, required cluster size, and installation. 
 [Documentation](https://www.ibm.com/docs/en/cloud-paks/cp-data) For more information such as postinstallation tasks and pricing. 







 Cloud Pak for Integration 



Cloud Pak for Integration

 Area Description 

 Use cases <br><br> * Integrate workflows, APIs, logging, and events across multiple cloud environments, all from a unified platform.<br> * Rapidly and securely transfer data across hybrid cloud environments.<br> * Set up a multichannel gateway to expand and control access to the full range of your mobile, web app, API, SOA, B2B, and other cloud workloads.<br><br><br> 
 [Catalog entry](https://cloud.ibm.com/catalog/content/ibm-cp-integrationabout) For included components, required cluster size, and installation. 
 [Documentation](https://www.ibm.com/docs/en/cloud-paks/cp-integration) For more information such as postinstallation tasks and pricing. 









 Cloud Pak for Security 



Cloud Pak for Security

 Area Description 

 Use cases <br><br> * Synchronize teamwork and playbooks to enhance security incident response.<br> * Increase threat hunting speed with a smart query builder, intelligent threat prioritization, and federated search.<br> * Real-time data security controls and audit visibility across hybrid cloud environments.<br><br><br>
Go to the [Discovery](https://cloud.ibm.com/catalog/services/watson-discovery) page in the IBM Cloud catalog and create a Plus plan service instance.



If you decide not to continue using the Plus plan and don't want to pay for it, delete the Plus plan service instance before the 30-day trial period ends.





 Create the search integration 



1. From the assistant where you want to add search, click Integrations.

You can add search if you are a user with a paid plan.
2. In the Extensions section, locate Search, click Add, then click Confirm.
3. Next, connect to a Discovery service instance.







 Connect to an existing Discovery instance 



1. Choose the Discovery service instance that you want to extract information from.

If you see a warning that some of your Discovery service instances do not have credentials set, it means that you can access at least one instance that you never opened from the IBM Cloud dashboard. You must access a service instance for credentials to be created for it, and credentials must exist before Watson Assistant can establish a connection to the Discovery service instance on your behalf. If you think a Discovery service instance is missing from the list, open the instance from the IBM Cloud® dashboard directly to generate credentials for it.
2. Indicate the data collection to use, by doing one of the following things:



* Choose an existing project.

You can click the Open Discovery icon to review the configuration of a project before you decide which one to use.

Go to [Configure the search](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-addsearch-add-configure).
* If you do not have a project or do not want to use any of the projects that are listed, click Create a new project to add one. Follow the steps in [Create a project](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-search-addsearch-add-create-discovery-collection).

Create a new project is not displayed if you reached the limits based on your Discovery service plan.
Customers will have the option to replace Pod Security Policies with [Pod security admission](https://kubernetes.io/docs/concepts/security/pod-security-admission/) or a [third party admission webhook](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/). IBM Cloud Kubernetes Service will make a beta version of Pod Security available in version 1.24 to aid in the migration, but this support is not yet available.

The following table shows the actions that you must take before you update the Kubernetes master.



Changes to make after you update the master to Kubernetes 1.24

 Type Description 

 IBM Cloud Block Storage driver and plug-in installation The IBM Cloud Block Storage driver and plug-in component is now installed on clusters running classic infrastructure. If you installed the IBM Cloud Block Storage driver and plug-in via the Helm chart, you must uninstall the Helm chart before continuing the master update. Note that your existing persistent volume claims (PVCs) will continue to work after the Helm chart is uninstalled, but you are not able to provision new PVCs until the master update is completed. To uninstall the Helm chart, see [Removing the Block Storage Helm chart](https://cloud.ibm.com/docs/containers?topic=containers-cs_versions_124124-rm-block-helm). 
 Updated default container network sysctls New containers running on the pod network will have the following sysctl tuning applied by default: net.ipv4.tcp_keepalive_intvl=15, net.ipv4.tcp_keepalive_probes=6 and net.ipv4.tcp_keepalive_time=40. If your apps rely on the previous defaults, you will need to update your app deployment to customize the sysctl settings. See [Optimizing network keepalive sysctl settings](https://cloud.ibm.com/docs/containers?topic=containers-kernelkeepalive-iks) for details. 





 Removing the Block Storage Helm chart 



1.
This appliance is the HCX-IX Interconnect Appliance (CGW) and is used to maintain a secure channel between vSphere environment that is designated as the source and the IBM Cloud. The following table shows the sizing specification of the CGW appliance that is deployed within the IBM Cloud.



Table 2. HCX-IX Interconnect Appliance deployment

 Component Configuration 

 CPU 8 vCPU 
 RAM 3 GB 
 Disk 2 GB VMDK resident on shared storage 



This HCX-IX Interconnect Appliance is deployed and configured to be on the management VLAN (Private Portable Subnet) and the vMotion VLAN (Private Portable Subnet) of the IBM Cloud for VMware Solutions deployment.

Additionally, another interface is configured on the Public VLAN (Public Portable) for connections that are made over the public internet. Public access is not required if a direct private connection is in place. The last connection that is associated with the HCX-IX Interconnect Appliance is a logical switch that is created and configured upon site pairing.

This logical switch is a private, non-routable network that is used as a communication channel between the HCX-IX Interconnect Appliance and HCX WAN Optimizer.





 WAN Optimizer 

The second component that is deployed is the WAN Optimization appliance. While the WAN Optimization appliance is optional, it performs WAN conditioning to reduce effects of latency. It also incorporates Forward Error Correction to negate packet loss scenarios, and deduplication of redundant traffic patterns.

Altogether, these reduce bandwidth use and ensure the best use of available network capacity to expedite data transfer to and from the IBM Cloud. The WAN Optimizer is disk intensive and requires sufficient amount of IOPS to function properly. As a result, the WAN optimizer is located on the vSAN storage, if present, or on the endurance storage with 2,000 IOPS.

The following table shows the sizing specification for the HCX WAN Optimization appliance.



Table 3. HCX WAN Optimizer appliance sizing

 Component Configuration 

 CPU 8 vCPU 
 RAM 14 GB
https://127.0.0.1:2005/ibm/console/login.do?action=secure

To enable ICC to use an SSL connection to IBM Cloud Object Storage (COS), which IBM COS requires, see [Configuring Cloud Storage Solutions file transfer encryption](https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_72/icc/topics/iccutsk_config_ssl.htm).



 Configuring ACS 

After starting ACS, create a system configuration (sysconfig).



1. Configure a server for localhost. For example, port 50000 is forwarding to port 23. Go into the 5250 session configuration and change the port from 23 to 50000.
2. Return to the IBM i terminal and enter your credentials, including System, User, and Password.
[Reboot all worker nodes in the cluster](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_worker_reboot). The worker nodes come back online with the default values applied.









 Optimizing pod performance 

If you have specific performance workload demands, you can change the default settings for the Linux kernel sysctl parameters on pod network namespaces.

To optimize kernel settings for app pods, you can insert an [initContainer](https://kubernetes.io/docs/concepts/workloads/pods/init-containers/) patch into the pod/ds/rs/deployment YAML for each deployment. The initContainer is added to each app deployment that is in the pod network namespace for which you want to optimize performance.

Before you begin, ensure you have the [Manager IBM Cloud IAM service access role](https://cloud.ibm.com/docs/containers?topic=containers-userschecking-perms) for all namespaces to run the sample privileged initContainer. After the containers for the deployments are initialized, the privileges are dropped.



1. Save the following initContainer patch in a file named pod-patch.yaml and add the fields and values for the sysctl parameters that you want to tune. This example initContainer changes the default maximum number of connections allowed in the environment via the net.core.somaxconn setting and the ephemeral port range via the net.ipv4.ip_local_port_range setting.

spec:
template:
spec:
initContainers:
- command:
- sh
- -c
- sysctl -e -w net.core.somaxconn=32768; sysctl -e -w net.ipv4.ip_local_port_range="1025 65535";
image: alpine:3.6
imagePullPolicy: IfNotPresent
name: sysctl
resources: {}
securityContext:
privileged: true
curl -X PUT https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/config/cloud_directory/sms_dispatcher/test --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer <IAMToken>' -d '{"phone_number": "+1 999 999 9999"}'









 Extending MFA 

With extensions, you can take the security of multifactor authentication to the next level. By making custom decisions about who is required to provide a second form of authentication, you can provide a more personal experience of your app for your users. You can also use extensions to audit MFA behaviors such as the number of failed second form authentications.



 Before you begin 

Before you register your extension, be sure that you have the following prerequisites:



* Your App ID instance's tenant ID. This ID can be found in the Applications section of the dashboard.
* Your Identity and Access Management (IAM) token. For help with obtaining an IAM token, check out the [IAM docs](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).



For more information about the restrictions and limitations of working with extensions, see [App ID limits](https://cloud.ibm.com/docs/appid?topic=appid-known-issues-limitslimits-extensions).





 Configuring pre-mfa 

With a pre-mfa extension, you can define the criteria that allows users to avoid having to enter a second form of authentication when they interact with your application.

Zoom

![pre-MFA flow](https://cloud.ibm.com/docs-content/v1/content/27ecaa7a29890634603881a8e64789974a29916b/appid/images/mfa-pre.png)

Figure 2. Cloud Directory pre-MFA flow



1.
In this section of the document, you will first demonstrate an existing, un-secure connection between a client and a queue manager, and then transform it into a TLS enabled, secure connection.

After enabling TLS on the queue manager's channel, the JMS application will need to be configured to trust the queue manager before it can communicate with it. First you will export the public part of the queue manager's security certificate. This part of the certificate is known as a public key. MQ on Cloud comes with a default security certificate, provided by Let's Encrypt R3. The JMS application will store the queue managers public key in a trust store. You will therefore create a trust store, and import the queue managers public key into it. The JMS application will then be updated to use the trust store.



 Step 1: Run unencrypted JMS application 

If your queue manager is version 9.2.1 revision 2 or higher, you will not be able to run JMS without TLS, move on to section 5.

You will have already run the JMS application if you have completed the prerequisites

The JMS application must be run to confirm that is runs, though the messages are not encrypted. Use the following commands depending on your operating system:



* Windows



* Recompile javac -cp .com.ibm.mq.allclient-9.0.4.0.jar;.javax.jms-api-2.0.1.jar comibmmqsamplesjmsJmsPutGet.java
* Run java -cp .com.ibm.mq.allclient-9.0.4.0.jar;.javax.jms-api-2.0.1.jar;. com.ibm.mq.samples.jms.JmsPutGet



* Linux



* Recompile javac -cp ./com.ibm.mq.allclient-9.0.4.0.jar:./javax.jms-api-2.0.1.jar com/ibm/mq/samples/jms/JmsPutGet.java
In the Security and Compliance Center navigation, click Settings.
3. In the Event Notifications section, and click Connect.
4. In the side panel, review the source details for the connection. Optionally, provide a description.
5. Select the resource group and Event Notifications service instance that you want to connect.

If an IAM authorization between Security and Compliance Center and Event Notifications doesn't exist in your account, a dialog is displayed. Follow the prompts to grant access between the services.



1. To grant access between Security and Compliance Center and Event Notifications, click Authorize.
2. In the side panel, select Event Notifications as the target service.
3. From the list of instances, select the Event Notifications service instance that you want to authorize.
4. Select the Event Source Manager role.
5. Click Review.
6. Click Assign.



6. To confirm the connection, click Connect.

A success message is displayed to indicate that Security and Compliance Center is now connected to Event Notifications. If you need to disconnect from Event Notifications later, you can use the options menu ![options icon](https://cloud.ibm.com/docs-content/v1/content/a6478671e8f845a84102d9cf49bf28ee7f4f3227/icons/actions-icon-vertical.svg)> Disconnect to remove the Security and Compliance Center as a source service in the Event Notifications instance.

If you choose to disconnect Event Notifications, do not delete the IAM authorization between Security and Compliance Center and Event Notifications. The Security and Compliance Center uses the existing authorization to unregister from Event Notifications. If an Event Notifications instance is deleted, any authorizations that exist between the service and Security and Compliance Center are also deleted by IAM.







 Connecting to Event Notifications with the API
This action creates and attaches a [virtual network interface](https://cloud.ibm.com/docs/vpc?topic=vpc-vni-about) to your mount target that identifies the file share with a reserved IP address and applies the rules of the selected Security group.



Table 4. Values for creating a mount target.

 Field Value 

 Details 
 Mount target name Specify a mount target name. The name can be up to 63 lowercase alpha-numeric characters and include the hyphen (-), and must begin with a lowercase letter. You can later edit the name if you want. 
 Zone Zone is inherited from the file share (for example, Dallas 2). 
 VPC Select an available VPC. The list includes only those VPCs with a subnet in the selected zone. 
 Subnet Select a subnet from the list. 
 Reserved IP address Required for the mount target. The IP address cannot be changed afterward. However, you can delete the mount target and create another one with a different IP address. 
 Reserving method You can have the file service select an IP address for you. The reserved IP becomes visible after the mount target is created. Or, specify your own IP. 
 Auto-release Releases the IP address when you delete the mount target. Enabled by default. 
 Security groups The security group for the VPC is selected by default, or select from the list. 
 Encryption in transit Disabled by default, click the toggle to enable. For more information about this feature, see [Encryption in transit - Securing mount connections between file share and host](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit). 



* If the share has VPC as the access mode, provide a name for the mount target and Select a VPC from the list.



5. Click Create.









 Create a file share from the CLI 



 Before you begin 



1. Before you can use the CLI, you must install the IBM Cloud CLI and the VPC CLI plug-in.
* Development team: This template promotes team alignment and resource monitoring by prioritizing a development or DevOps workflow.
* Management: Optimized to provide a mix of billing, access management, and other administrative widgets.



3. Enter dashboard title. The title must be 30 characters or less.
4. Next, use the Dashboard settings pane to add relevant widgets to your dashboard. To add widgets, drag the widgets onto your dashboard.
5. Click the Scope tab to select from the available resources in the account that you have access to. The scope determines the data that populates for the selected resources. You can filter the resource by group, tag, and location.

Not all widgets can be scoped. If a widget can't be scoped, it displays data for all resources.
6. Click Save dashboard.



Any dashboard that is shared with you appears on your dashboards page.



 Managing your dashboard 

After you create a dashboard, you can manage your dashboard by in the IBM Cloud console by going to Manage > Account, and selecting Account resources > Dashboards. Or, from your dashboard click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Manage my dashboards.







 Sharing a dashboard 

You can share dashboards with users in your account to give them access to view the dashboard. All users with the dashboard link can share the dashboard.

To share a dashboard, complete the following steps:



1. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg).
2. Select Share. After you share it with a user and they click the link, the dashboard is added to their account.
+ scheduled_reclaim_at = (known after apply)
+ scheduled_reclaim_by = (known after apply)
+ service = "event-notifications"
+ service_endpoints = (known after apply)
+ state = (known after apply)
+ status = (known after apply)
+ sub_type = (known after apply)
+ tags = (known after apply)
+ target_crn = (known after apply)
+ type = (known after apply)
+ update_at = (known after apply)
+ update_by = (known after apply)
}
Show more







 Step 5: Exporting an API key 

Export your IBM Cloud API Key before running the apply command:

export IBMCLOUD_API_KEY={Your IBM Cloud API Key}





 Step 6: Running Terraform applyapply 

The Terraform apply command implements the changes that are declared during the plan step and deploys the resource to the IBM Cloud.

bash-5.1 terraform apply

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create

Terraform will perform the following actions:

 ibm_en_destination.destination1 will be created
+ resource "ibm_en_destination" "destination1" {
+ description = "Smart House device status"
+ destination_id = (known after apply)
+ id = (known after apply)
+ instance_guid = (known after apply)
+ name = "Smart Home Android app"
+ subscription_count = (known after apply)
+ subscription_names = (known after apply)
+ type = "webhook"
+ updated_at = (known after apply)

+ config {
+ params {
+ custom_headers = {
+ "authorization" = "secure"
}
+ sensitive_headers = [
+ "authorization",
]
+ url = "https://hello.demo.com/hello"
+ verb = "POST"
}
}
}