vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Use projects to [configure and deploy a deployable architecture](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-config-project). 
 Running templates locally by using Terraform directly N/A Customer can run the deployable architecture on their local system. 
 Customize modules or deployable architectures with pre-supported modules IBM provides and supports base Terraform modules for services on IBM Cloud, and provides preset JSON configuration overrides for templates. Customer can use these base Terraform modules to extend their base deployable architecture pattern. 
 Workload Management (Application Migration and Backup/Restore) N/A Customer responsibility to manage and migrate application workloads. 
 Fixes, new features, and updates to the next major deployable architecture release IBM provides regular updates, bug fixes, and new features in a continuous delivery model that is apparent to the customer. IBM provides a migration path when possible. N/A 
 Keep deployed services and resources up to date N/A Apply fixes and updates to the compute resources that are created from the deployable architecture. These resources are not updated through the deployable architecture unless otherwise indicated. 
 Issues found in IBM-provided versions of Terraform modules IBM provides a way for customers to open issues. If the issue is with a deployable architecture, open a case. If the issue is with a module, open an issue in the module [GitHub repo](https://github.com/terraform-ibm-modules). Customer provides information to reproduce any problem. 
 Issues with IBM container images IBM provides a way for customers to open issues. Customer provides information to reproduce any problem. 
 Issues with third party and open source container images N/A Customer resolves with third-party vendor or open source community. 
 Issues with IBM Cloud-provided stock operating system images N/A Customer must get a compatible stock image from the vendor. 
 Issues with the services that the Terraform creates from a deployable architecture IBM Cloud resolves issues with the services. N/A
Known issues 

Review the following known issues that you might encounter while you work with IBM Cloud® Security and Compliance Center.



Table 1. Known issues and workarounds

 Issue                                     Workaround                                                                                                                                                   

 You cannot create a second integration.   Only one integration can be created for each name or URL. If you need to update your integration in some way, delete the integration and create a new one.
For example, https://1a619c43-6425-4abb-8df0-0c7b1b3a3001.8f7bfd8f3faa4218aec56e069eb46187.databases.appdomain.cloud:31797/api/

The API uses application/json data and requires basic authentication. You can use any user that you created on your deployment to access the UI. However, some features might be available only to the admin user.

Documentation and examples are provided with your deployment at the browser URL with /api/index.html. For example, https://1a619c43-6425-4abb-8df0-0c7b1b3a3001.8f7bfd8f3faa4218aec56e069eb46187.databases.appdomain.cloud:31797/api/index.html





 Installing rabbitmqadmin 

The rabbitmqadmin binary is available directly from your deployment. The download and installation instructions are found on /cli page of the management plug-in. For example, https://1a619c43-6425-4abb-8df0-0c7b1b3a3001.8f7bfd8f3faa4218aec56e069eb46187.databases.appdomain.cloud:31797/cli

rabbitmqadmin is also available with a full, local installation of the RabbitMQ package. However, if the version of the package you download doesn't match the deployment's RabbitMQ version, it might not connect.





 Connecting with rabbitmqadmin 

The rabbitmqadmin connection information is in the "cli" section of your [connection strings](https://cloud.ibm.com/docs/messages-for-rabbitmq?topic=messages-for-rabbitmq-connection-strings). The table contains a breakdown for reference.



Table 1. rabbitmqadmin/cli connection information

 Field Name Index Description
Migrating details from Node.js 12 to Node.js 16

 Package Details 

 cloudant The @cloudant/cloudant SDK package in the nodejs:12 runtime is deprecated and has been replaced with @ibm-cloud/cloudant in nodejs:16. This is a major change and will cause incompatibilities, which might cause your action to fail. If your action uses @cloudant/cloudant consider migrating to @ibm-cloud/cloudant. For more information about migrating to ibm-watson v6.x, see [Migrating to the cloudant-node-sdk](https://github.com/cloudant/nodejs-cloudant/blob/master/MIGRATION.md). <br>If you can't migrate, consider packaging @cloudant/cloudant with your action as described in [Packaging JavaScript code as NPM files](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_js_npm). For more information about the @ibm-cloud/cloudant SDK look at the [IBM Cloudant Docs](https://cloud.ibm.com/apidocs/cloudant?code=node). 
 redis The redis package in the nodejs:16 runtime is at version v4.x. <br>Major version changes can introduce incompatibilities, which might cause your action to fail. If your action uses an earlier version of this package, consider migrating to the current version. For more information about migrating to redis v4, see [v3 to v4 Migration Guide](https://github.com/redis/node-redis/blob/master/docs/v3-to-v4.md). <br>If you can't migrate, consider packaging the older version of redis package with your action as described in [Packaging JavaScript code as NPM files](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_js_npm).
Using Java 

The IBM Analytics Engine SDK for Java provides features that allow you to interact programmatically with the IBM Analytics Engine service API for serverless instances.

The source code can be found in this [GitHub repository](https://github.com/IBM/ibm-iae-java-sdk).



 Getting the SDK 

The easiest way to use the IBM Analytics Engine Java SDK is to use Maven to manage library dependencies. If you aren't familiar with Maven, see [Maven in 5-Minutes](https://maven.apache.org/guides/getting-started/maven-in-five-minutes.html).

Maven uses a file that is called pom.xml to specify the libraries and their versions needed for a Java project. Here is an example of the pom.xml file for using the IBM Analytics Engine Java SDK to connect to IBM Analytics Engine.

<dependency>
<groupId>com.ibm.cloud</groupId>
<artifactId>ibm-analytics-engine-api</artifactId>
<version>0.4.2</version>
</dependency>





 Creating a client and sourcing credentials 

When you connect to IBM Analytics Engine, a client is created and configured using the credential information (API key and service instance ID) that you provide. If you don't provide this information manually, these credentials can be sourced from a credentials file or from environment variables.

You can retrieve the service instance ID when you create service credentials or through the CLI. See [Retrieving service endpoints](https://cloud.ibm.com/docs/AnalyticsEngine?topic=AnalyticsEngine-retrieve-endpoints-serverless).

To use the IBM Analytics Engine Java SDK, you need the following values:



* IAM_API_KEY: The API key generated when creating the service credentials. You can retrieve by viewing the service credentials on the [IBM Cloud dashboard](https://cloud.ibm.com/resources).
* instance_guid: The value in resource_instance_id generated when the service credentials are created.
Why are my attributes showing the wrong values? 

You encounter issues with the values your attributes.

  What’s happening 

An attribute value exists in a user profile, but it's not associated with the correct attribute.

  Why it’s happening 

The user profile attribute is not mapped correctly.

  How to fix it 

Map the attribute in your identity provider settings. App ID expects the following attributes:



*  name
*  email
*  locale
*  picture
const myService = new ExampleServiceV1({
authenticator,
});
...

// Later when the access token expires, the application must acquire
// a new access token, then set it on the authenticator.
// Subsequent request invocations will include the new access token.
authenticator.setBearerToken('<new-access-token>')

Use the same IAM access token for subsequent IBM Cloud service API calls to achieve the best performance and scalability.

[Java SDK reference](https://github.com/IBM/java-sdk-core/blob/main/Authentication.mdbearer-token-authentication)

[Node SDK reference](https://github.com/IBM/ibm-cloud-sdk-common/blob/main/README.md3-create-a-bearer-token-authenticator-programmatically)

[Python SDK reference](https://github.com/IBM/ibm-cloud-sdk-common/blob/main/README.md3-create-a-bearer-token-authenticator-programmatically)

[Go SDK reference](https://github.com/IBM/go-sdk-core/blob/main/Authentication.mdbearer-token-authentication)





 Passing an IBM Cloud API key to authenticate with a service API 

API clients can directly pass an IBM Cloud API key to the target service’s API. To do so, send the apikey keyword as the user name and the IBM Cloud API key as the password by using basic authorization HTTP header to the target service.

It is recommended that in all cases of passing an API key to a service API that you use an API key for a service ID or a user API key that is associated with a functional ID that is assigned only the level of access required to work with the particular service.

The target service API must introspect the IBM Cloud API key by using the IBM Cloud IAM service. The following graphic shows three API interactions.
With a default configuration, VRRP is enabled to perform preemption, which means that a new higher priority peer on the network forces failover of the Master role.

When preemption is disabled, a higher priority peer will only failover the Master role if the existing lower priority peer is no longer available on the network. Disabling preemption is sometimes useful in real world scenarios, as it copes better with situations where the higher priority peer might have started to periodically flap due to reliability issues with the peer itself or one of its network connections. It is also useful to prevent the premature failover to a new higher priority peer which has not completed network convergence.





 Assumptions and limitations of preemption 

If the VRRP peers are configured to disable preemption, then there are some cases where preemption may “appear” to occur, but in reality the scenario is just a standard VRRP failover. As described above, VRRP makes use of IP multicast datagrams as a means to confirm availability of the currently elected Master router. Since it is a layer 3 protocol that is detecting failure of a VRRP peer, it is important that failover detection in VRRP is delayed until VRRP and the layer 1 through 2 of the network stack is ready and converged. In some cases, the network interface running VRRP might confirm to the protocol that the interface is up, but other underlying services like Spanning Tree, or Bonding might not have completed. As a result, IP connectivity between peers cannot be established. If this occurs, VRRP on a new higher peer becomes Master as it is unable to detect VRRP messages from the current Master peer on the network. After convergence, the brief period of time when there is two Master VRRP peers results in the dual Master logic of VRRP being executed. The higher priority peer remains Master, and the lower priority becomes backup. This scenario might appear to demonstrate a failure in the “no preemption” functionality.





 Start Delay feature 

To accommodate the issues associated with delay in convergence of the lower levels of the network stack during an interface up event, as well as other contributory factors, a new feature called “Startup Delay” is introduced in the 1801p patch.
For more information, see [Viewing details of an endpoint gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-viewing-details-of-an-endpoint-gateway).



Now your virtual server instances in the VPC can access your DNS Services instance privately through it.







 Using your VPE for DNS Services 

After you create an endpoint gateway for DNS Services, follow these steps:



 Using the VPE with the CLI 

Use the following steps to update to the latest version of the CLI and the DNS Services plug-in.



1. Update the IBM Cloud CLI to the latest version:

ibmcloud update
2. Update the DNS Services CLI plug-in:

ibmcloud plugin update cloud-dns-services
3. Log into private.cloud.ibm.com. For more information about logging into the private cloud, see [Securing your connection when using the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-service-connection).







 Using the VPE with the VPC API 

After creating an endpoint gateway for the DNS Services service, use the service endpoints FQDN api.private.dns-svcs.cloud.ibm.com in the URL to access the service. For example:

curl https://api.private.dns-svcs.cloud.ibm.com/v1/dns-svcs?version='2020-03-31' -H "Authorization: Bearer $iam_token"





 Using the VPE with the SDK 

After creating an endpoint gateway for DNS Services, you must use the private endpoint's FQDN when setting the service's FQDN during construction of the DNS Services gateway service object.

api.private.dns-svcs.cloud.ibm.com

For examples of setting the service's FQDN for the specific SDK language, see [SDK API examples](https://cloud.ibm.com/apidocs/dns-svcs?code=goauthentication).
Common issues when creating a new load balancer 

This topic rovides information on common issues that you might encounter when creating a new instance of IBM Cloud® Load Balancer.



  Insufficient IP addresses in your subnet 

IBM Cloud® Load Balancer requires at least two free IP addresses from its private subnet. In addition, if the load balancer is a public load balancer and the IBM system pool option is not used, then at least two free IP addresses are needed from your public subnet as well.





  Issues with firewalls on public and private VLANs 

For more information, see [IBM Cloud IP ranges](https://cloud.ibm.com/docs/hardware-firewall-dedicated?topic=hardware-firewall-dedicated-ibm-cloud-ip-rangesibm-cloud-ip-ranges).





  Viewing load balancer error messages 

To view error messages for your load balancer, follow these steps:



1.  Click the load balancer from the list page to view its details.
2.  Mouseover the error symbol next to the load balancer's status.



If the load balancer is in an ERROR state, it cannot be recovered and must be deleted.
Table 1. File storage lifecycle states

 Status Explanation 

 Stable The file share or mount target is stable and available for use. 
 Pending The file share or mount target is being created. 
 Failed The file share or mount target failed to be created. You can delete the failed share and try creating another one. 
 Deleting The file share or mount target is being deleted. 
 Deleted The file share or mount target is deleted. 
 Initializing The file share replica is being created. 
 Split_pending The replica file share is being split from the source share. 
 Failover_pending The source file share is failing over to the replica file share, which becomes read/write and the new source share. 







 Managing security and compliance 

File Storage for VPC is integrated with the Security and Compliance Center to help you manage security and compliance for your organization. You can set up goals that check whether file shares are encrypted by using customer-managed keys. By using the Security and Compliance Center to validate the file service configurations in your account against a profile, you can identify potential issues as they arise.

For more information, see [Monitoring security and compliance posture with VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-security-compliancemonitor-vpc). For more information about creating security and compliance goals, see [Defining rules](https://cloud.ibm.com/docs/security-compliance?topic=security-compliance-rules-define&interface=ui) in the Security and Compliance documentation.





 Limitations in this release 

The following limitations apply to this release of File Storage for VPC.



* File share size cannot be increased after it is created.
* Previous profiles are not supported when you provision a new file share, which is based on the dp2 profile. However, earlier version file shares can continue to use existing profiles.
* Restricting file share access to specific virtual server instances and data encryption in transit is available only for shares that are based on the dp2 profile.
* Windows operating systems are not supported.
* Minimum capacity is 10 GB per file share.
* Maximum capacity is 32,000 GB per file share.
The configuration in the .pipeline-config.yaml file supports the following parameters:

These settings are not pipeline parameters, they must be part of your .pipeline-config.yaml file.



* image: You can use any Docker image that is accessible by the pipeline worker as a base image for the task.
* script: The script to run in the stage. Because this field is used as a script file, ensure that the contents act like a script file in the base image that you provided. You can include other scripts next to this configuration file, and refer to them from this entry point. For example:



test:
image: ibmcom/pipeline-base-image:2.7
script: 
!/bin/sh
scripts/lint.sh
scripts/unit-test.sh



* dind: Specify whether to enable docker-in-docker for the script context. The default setting is false.
* abort_on_failure: By default, the pipeline stops when the script fails. Setting this to false marks the stage in a warning (amber state) (it passed with warning), allows the pipeline to continue, and lets the failed job be referenced in the evidence later.
* image_pull_policy: Set the pod ImagePullPolicy setting that is provided in the image, for the base image. Possible values are the same as valid values for Kubernetes: Always or IfNotPresent. The default value is IfNotPresent.
* configmap: Pull key-value pairs from a provided configmap that is accessible by PipelineRun. The following values are supported:



* config-name: The direct configmap name syntax. The stage runner tries to access and mount the configmap named config-name.
* $prop-name: The indirect configmap name syntax. The configmap name is looked up from the environment-properties configmap, which contains every environment value that is set on the pipeline UI. For example, if there is a prop: my-config entry in the environment properties, then my-config is used for $prop.
Start speed is especially important for Code Engine applications that are based on Knative. Such applications can be configured to scale down to zero running instances when there is no traffic, thus consuming no resources and costing no money. When a request comes in, an instance is started to handle the request. Your container must start as fast as possible to respond to the new request.

To improve the startup of your application, investigate the implementation of your application and see whether you can apply patterns such as:



* Parallelization of independent initialization work, for example, to establish a connection to a database and to read the configuration file to communicate with a mail server from environment variables.
* Delaying of initialization work that is not needed for application startup and instead perform them on first need basis.



In addition, you can also avoid a common pitfall when you implement a web application that uses a framework such as Angular, React, or Vue. Each of these frameworks is based on Node.js with NPM and includes a command-line interface that can make it easy to set up a project. For example, a React application that is created with the [create-react-app](https://github.com/facebook/create-react-app) command sets up a package.json file that includes some predefined scripts. One of these scripts is start, which brings up a web server with your web application. Your Dockerfile can look similar to the following example,

FROM nodejs:16-alpine

COPY . /app
WORKDIR /app

RUN npm install

EXPOSE 3000
ENTRYPOINT ["npm", "run", "start"]

While this type of Dockerfile works, it is not fast as whenever the npm run start command is invoked, the application is compiled and then started. This delay is especially noticeable with applications that go beyond a small sample size. The correct approach is to compile the application at build time and serve it only at startup,

FROM node:16-alpine AS builder

COPY . /app
WORKDIR /app

RUN npm install && npm run build

FROM node:16-alpine

RUN npm install -g serve
This change comes with a number of bug-fixes and improvements made by the community.
* The Node.js buildpack now comes with [IBM SDK for Node.js v1.1.0.13](https://developer.ibm.com/languages/node-js/articles/download-nodejs-for-ibm-platforms/).







 20 March 2015 

Updated Liberty buildpack v1.14-20150319-1159
: This version of the buildpack contains an updated IBM JRE 7.1.2.11 with a security fix for the [FREAK vulnerability](https://www.ibm.com/blogs/psirt/ibm-security-bulletin-freak-vulnerability-fixed-in-liberty-for-java-for-ibm-bluemix-cve-2015-0138/).



* The [SQL Database](https://cloud.ibm.com/docs/sql-query?topic=sql-query-gettingstarted) service offers paid plans that provide an option for connecting with the database server over the SSL protocol. The buildpack's auto-configuration support for SQL Database service was updated to configure the runtime to connect with the database over SSL if the SSL connection information is available.
* The buildpack was updated to report an error when a stand-alone WAR or EAR file that contains a server.xml configuration file in root of the app archive is deployed.
* The buildpack contains a fix for MongoDB's auto-configuration service plug-in that in certain cases generated an invalid server.xml configuration.







 10 February 2015 

Updated Liberty buildpack v1.13-20150209-1122
: The buildpack contains security fixes for the [Apache HttpComponents and Java overlay feature vulnerabilities](https://www.ibm.com/blogs/psirt/ibm-security-bulletin-multiple-vulnerabilities-fixed-in-liberty-for-java-for-ibm-bluemix-cve-2012-6153-cve-2014-3577-cve-2015-0178/).