vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You will need the appropriate [region](https://cloud.ibm.com/docs/cloud-object-storage?topic=cloud-object-storage-endpointsendpoints-region) for your bucket and endpoint.

Sys.setenv("AWS_ACCESS_KEY_ID" = "access_key_id",
"AWS_SECRET_ACCESS_KEY" = "secret_access_key",
"AWS_S3_ENDPOINT" = "myendpoint",
"AWS_DEFAULT_REGION" = "")





 Add libraries to your R project 

We used a cloudyr[S3-compatible client](https://github.com/cloudyr/aws.s3) to test our credentials resulting in listing your buckets. To get additional packages, we use the source code collective known as [CRAN](https://cran.r-project.org/) that operates through a series of [mirrors](https://cran.r-project.org/mirmon_report.html).

For this example, we use [aws.s3](https://cran.r-project.org/package=aws.s3) as shown in the example and added to the code to set or access your credentials.

library("aws.s3")
bucketlist()



 Use library methods in your R project 

You can learn a lot from working with sample packages. For example, the package for [Cosmic Microwave Background Data Analysis](https://github.com/frycast/rcosmo) presents a conundrum. The executable of the project for local compiling are small enough to work on one's personal machine, but working with the source data would be constrained due to the size of the data.

When using version 0.3.21 of the package, it is necessary to add region="" in a request to connect to COS.

In addition to PUT, HEAD, and other compatible API commands, we can GET objects as shown with the S3-compatible client we included earlier.

 return object using 'S3 URI' syntax, with progress bar
An example of Hybrid Cloud used with SAP S/4HANA when exceeding 14-18TB of DRAM, would be the use of IBM Power9 hardware provided by IBM Power Systems, deployed into Traditional On-Premises datacenters. The maximum IBM Power9 hardware can support 28TB of DRAM for SAP HANA 2.0 scale-up. These complementary offerings are already succesfully running many customers SAP workloads at these largest memory footprints, through a close partnership and engineering discussions with SAP, therefore may suit the business needs for such exceptional scale-up requirements. For more information regarding SAP HANA on IBM Power Systems, see [SAP Note 2188482 - SAP HANA on IBM Power Systems: Allowed Hardware](https://launchpad.support.sap.com//notes/2188482).







 SAP NetWeaver considerations 

The SAP S/4HANA business application is impacted by multiple [SAP NetWeaver Application Server design considerations](https://cloud.ibm.com/docs/sap?topic=sap-netweaver-design-considerations).



 Versioning and upgrades 

SAP S/4HANA no longer has a stand-alone shipment of SAP NetWeaver Application Server (ABAP) which can be used.

The SAP S/4HANA Server component is required to install SAP S/4HANA. This component is briefly titled as SAP ABAP Platform and historically called SAP NetWeaver AS ABAP.

For SAP S/4HANA "AnyPremise" 20xx (for example, 2020), the SAP S/4HANA Server contains:



* SAP ABAP Platform 20xx and SAP Kernel 7.7x (the version number of these components are only shown after the installation is completed)
* ADT for Eclipse
* Other additional technology components to run SAP S/4HANA



For this reason, when you are running older SAP S/4HANA versions (such as 1511, 1610, 1709) it is not possible to upgrade SAP NetWeaver AS ABAP 7.5+ in isolation. All upgrades must be handled by using SAP Maintenance Planner for the entire stack on a specified OS (for example, Red Hat Linux®, SUSE Linux, IBM AIX, Windows Server).
- name: provider_source
value: IBM-Cloud/ibm
- name: region
value: us-south





 module.injectors.tft_git_url 

Type: URL

Required: true







 module.injectors.tft_name 

Type: string

Required: true

Name of the template file to use

ibm





 module.injectors.injection_type 

Type: string

Required: true

Two modes of injection are supported by Terraform. Definitions can be injected as extra files, only if it is believed that no conflict with any existing HCL statements. Alternatively they can be injected as [HCL override files](https://developer.hashicorp.com/terraform/language/files/override).

override





 module.injectors.tft_parameters 

Type: list

Required: true

A list that defines the templating inputs as name-value pairs. At this time, only static values are supported.

Example

- name: provider_version
value: 1.42.3
- name: provider_source
value: IBM-Cloud/ibm
- name: region
value: us-south
CE_ID=abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
CE_SOURCE=/apis/v1/namespaces/1234abcd1a2/pingsources/mycroneventjob
CE_SPECVERSION=1.0
CE_TIME=2021-04-13T17:41:00.429658447Z
CE_TYPE=dev.knative.sources.ping
CONTENT_TYPE=application/json
HOME=/root
HOSTNAME=myjob-mpps4-0-0
JOB_INDEX=0
KUBERNETES_PORT=tcp://172.21.0.1:443
KUBERNETES_PORT_443_TCP=tcp://172.21.0.1:443
KUBERNETES_PORT_443_TCP_ADDR=172.21.0.1
KUBERNETES_PORT_443_TCP_PORT=443
KUBERNETES_PORT_443_TCP_PROTO=tcp
KUBERNETES_SERVICE_HOST=172.21.0.1
KUBERNETES_SERVICE_PORT=443
KUBERNETES_SERVICE_PORT_HTTPS=443
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PWD=/
SHLVL=1

Note that log information for job runs lasts for only one hour. For more information about logging, see [Viewing logs](https://cloud.ibm.com/docs/codeengine?topic=codeengine-view-logs).

For more information about the environment variables that are sent by cron, see [Environment variables for events](https://cloud.ibm.com/docs/codeengine?topic=codeengine-subscribe-cronsub-envir-variables-cron).

Looking for more code examples?
When available, the claims are mapped directly from your identity provider to the token by default. The claims can't be explicitly omitted but they can be overwritten in your token by custom claims. The claims include name, email, picture, and locale.

Restricted claims
: Restricted claims are those that have limited customization possibilities and cannot be overwritten by custom mappings. For an access token, scope is the only restricted claim. Although it cannot be overwritten, it can be extended with your own scope. When a scope is mapped to an access token, the value must be a string and cannot be prefixed by appid_ or it is ignored. In identity tokens, the claims identities and oauth_clients cannot be modified or overwritten.

Registered claims
: Registered claims are present in your access and identity tokens and are defined by App ID. They cannot be overridden by custom mappings. These claims are ignored by the service and include iss, aud, sub, iat, exp, amr, and tenant.

Defining a claim for your token does not change or eliminate [the attribute](https://cloud.ibm.com/docs/appid?topic=appid-profiles). It changes the information that is present in the token at run time.





 How are claims mapped to tokens? 

Each mapping is defined by a data source object and a key that is used to retrieve the claim. You can inject up to 100 claims into each token if the maximum payload remains less than 100 KB. If you want to use nested claims, you can include them by using the dot syntax. For example, nested.attribute.

The claims are set for each token separately and are sequentially applied as shown in the following example.

{
"accessTokenClaims": [
{
"source": "saml",
"sourceClaim": "moderator"
},
{
"source": "saml",
"sourceClaim": "viewer",
"destinationClaim": "reader"
}
],
"idTokenClaims": [
{
Click Create.
5. In the Source service menu, select the service of the deployment. For example, Databases for PostgreSQL or Messages for RabbitMQ
6. In the Source service instance menu, select All instances.
7. In the Target service menu, select HPCS.
8. Select or retain the default value Account as the resource group for the Target Service
9. In the Target service Instance ID menu, select the service instances to authorize.
10. Enable the Reader role.
11. Click Authorize.



If the service authorization is not present before provisioning your deployment with a key, the provision fails.





 Using the HPCS Key 

After you grant your Cloud Databases deployments permission to use your keys, you supply the [key name or CRN](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-view-keys) when you provision a deployment. The deployment uses your encryption key to encrypt your data.

If provisioning from the catalog page, select the HPCS instance and key from the dropdown menus.

In the CLI, use the disk_encryption_key_crn parameter in the parameters JSON object.

ibmcloud resource service-instance-create example-database <service-name> standard us-south -p '{
"disk_encryption_key_crn": "crn:v1:<...>:key:<id>"
}'

In the API, use the disk-encryption-key parameter in the body of the request.

curl -X POST https://resource-controller.cloud.ibm.com/v2/resource_instances -H 'Authorization: Bearer <>' -H 'Content-Type: application/json' -d '{
"name": "my-instance",
"target": "blue-us-south",
"resource_group": "5g9f447903254bb58972a2f3f5a4c711",
"resource_plan_id": "databases-for-x-standard",
The following example creates a snapshot of the volume with the ID r010-bdb8fc70-8afb-4622-826a-d65a9fc477a4. The snapshot is named example-snapshot. In addition, two fast restore clones of the snapshot are created in eu-de-1 and eu-de-3 regions.

resource "ibm_is_snapshot" "example_clones" {
name = "example-snapshot-clone"
source_volume = "r010-bdb8fc70-8afb-4622-826a-d65a9fc477a4"
clones = ["eu-de-1", "eu-de-3"]
}

For more information about the arguments and attributes, see [ibm_is_snapshot](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/is_snapshot).





 Create a cross-regional copy of a snapshot with Terraform 

To create a copy of snapshot in a remote region, use the ibm_is_snapshot resource. The following example creates a copy in the target region by using the CRN of the source snapshot. The copy is going to be encrypted by the encryption key that is specified by its CRN.

resource "ibm_is_snapshot" "snapshot" {
name 		 = "my-cross-regional-snapshot"
source_snapshot = "r138-4463eb2c-4913-43b1-b9bf-62a94f74c146"
encryption_key = "crn:v1:staging:public:kms:us-south:a/df0564dd126042ebb03e0224728ce939:4957299d-0ba0-487f-a1a0-c724a729b8b4:key:0cb88b98-9261-4d07-8329-8f594b6641b5"
}
x-amz-copy-source-if-unmodified-since String (time stamp) Creates a copy if the source object has not been modified since the specified date. Date must be a valid HTTP date (for example, Wed, 30 Nov 2016 20:21:38 GMT). 
 x-amz-copy-source-if-modified-since String (time stamp) Creates a copy if the source object has been modified since the specified date. Date must be a valid HTTP date (for example, Wed, 30 Nov 2016 20:21:38 GMT). 



Example request

This basic example takes the bee object from the garden bucket, and creates a copy in the apiary bucket with the new key wild-bee.

PUT /apiary/wild-bee HTTP/1.1
Authorization: Bearer {token}
x-amz-copy-source: /garden/bee
Host: s3.us.cloud-object-storage.appdomain.cloud

Example request

PUT /apiary/wild-bee HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
x-amz-copy-source: /garden/bee
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response

HTTP/1.1 200 OK
Date: Wed, 30 Nov 2016 19:52:52 GMT
X-Clv-Request-Id: 72992a90-8f86-433f-b1a4-7b1b33714bed
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.137
X-Clv-S3-Version: 2.5
x-amz-request-id: 72992a90-8f86-433f-b1a4-7b1b33714bed
Updating data source information 

When you open an existing dashboard asset, the underlying data source may have changed since the dashboard specification was last saved. Possible changes are:



*  New credentials, for example a changed password, for accessing the data source.
*  New columns are added to the data source.



The dashboardAPI.getSpec() method returns all definitions of data source that were previously passed in to dashboardAPI.addSources() calls. To allow your embedding app to update these data source module definitions, you must use the updateModuleDefinitions() method before you open the saved dashboard specification. This method takes two parameters:



*  Old dashboard specification
*  Data source updater callback function



The callback function is passed in the list of module ids, and is responsible for returning a list of the updated data source definitions. This list of updated data source definitions has the same format as being in the addSources() method. In turn, use the updateModuleDefinitions() method to return the updated dashboard specification. You can use this updated dashboard specification then in the openDashboard() call.

Example flow of how to open a dashboard:

![opendashboardflow](https://cloud.ibm.com/docs-content/v1/content/2781097afe16f2d329d7a606ddd260fb1a3e355c/services/cognos-dashboard-embedded//images/opendashboardflow.svg)



*  WDP: Watson Data Platform
*  DSX: Data Science Experience
[Configuring a highly available application](https://cloud.ibm.com/docs/codeengine?topic=codeengine-deploy-multiple-regions)Configuring a highly available application

You can deploy your IBM Cloud® Code Engine application across multiple regions to make it resilient to regional failures. Note that this example uses IBM Cloud Internet Services, but you can use alternate providers. This example also uses a custom domain.

Code Engine Cloud Internet Services (CIS)



* 30 minutes
* 2023-04-20



[Setting up a web application firewall with F5 BIG-IP](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-waf-tutorial)Setting up a web application firewall with F5 BIG-IP

There are several architectural approaches to enabling consumer connectivity to the workload VPC. When using public internet access to the workload VPC, a web application firewall (WAF) is required. A WAF helps protect web applications by filtering and monitoring internet traffic. This tutorial guides you through one approach to enabling WAF by using IBM Cloud® Internet Services (CIS) and F5 BIG-IP Virtual Edition. Global load balancing along with a WAF forms the basis for you to meet IBM Cloud Framework for Financial Services requirements for boundary protection.

Cloud Internet Services (CIS) Virtual Private Cloud (VPC)

+2

,IBM Cloud Framework for Financial Services



* 4 hours
* 2022-03-23



[Deploying server pools and origins in a single MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-pools-origins)Deploying server pools and origins in a single MZR

Use this tutorial to deploy availability pools in a VPC for a single MZR. Creating server pools with origins provides your DevOps team with a staging environment so they can validate near-production ready code in parallel with an existing production environment.

Virtual Servers for Classic Virtual Private Cloud (VPC)

+3
With the ibm_schematics_state data source, you automatically have access to the built-in Schematics backend and can access workspace information directly.

What do I need to do to access resource information in other workspaces?
Similar to the remote_state data source, you can only access information that you configured as output values in your Terraform template. For example, let's say you have a workspace that you used to provision a VPC. To access the VPC ID, you must define the ID as an output variable in your Terraform configuration file.

To use the ibm_schematics_output data source:



1. Follow the example in the [getting started tutorial](https://cloud.ibm.com/docs/schematics?topic=schematics-getting-started) to create a Schematics Workspaces and provision a virtual server in a VPC. As you follow the instructions, review the output variables that are defined at the end of the vpc.tf Terraform configuration file.

If you already used a different Terraform configuration file in one of your workspaces, you can use this workspace for the exercise. Make sure to add output values as outlined in this example to your configuration file so that you can access your workspace information later.

output sshcommand {
value = "ssh root@ibm_is_floating_ip.fip1.address"
}

output vpc_id {
value = ibm_is_vpc.vpc.id
}

In this example, two output values are defined, the sshcommand to access the virtual server instance in your VPC and the vpc_id.
2. Retrieve the ID of the VPC workspace that you created.

Through console:



* From the [workspace dashboard !
[Juniper® vSRX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-juniper-overview) 3.0 (23.1R2) 
 [Red Hat OpenShift for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-ocp_overview) 4.12 
 [Veeam®](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview) 12 
 [VMware Aria Operations and VMware Aria Operations for Logs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrops_overview) VMware Aria® Operations™ 8.12 and VMware Aria Operations™ for Logs 8.12 
 [Zerto](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-addingzertodr) 9.7u3 







 Promotions for services 

IBM Cloud® for VMware Solutions offers promotion pricing for some services. The promotions offer a number of months at no cost for service licenses, if the service has license charges.

You can use one promotion (promo) code for one or more services when you:



* Order a new Cyber Recovery instance
* Add a service to a Cyber Recovery instance
* Order a stand-alone service license, such as Caveonix or Veeam



For services that charge per host, promo codes apply only to the hosts in the order or in the current environment. Examples of such services are HCX, Entrust CloudControl, and VMware Aria® Operations™ and VMware Aria Operations™ for Logs.

You can use one promo code per order. Multiple promo codes are not allowed. However, you can use a promo code multiple times per account. A promo code might apply to multiple services, for example, Veeam and Caveonix RiskForesight.
Download the https://github.com/IBM/CodeEngine sample source to your local workstation with the following command.

git clone https://github.com/IBM/CodeEngine
2. Change to the CodeEnginehelloworld directory.
3. From the CodeEnginehelloworld directory, run a build run to build an image from the helloworld source on your local workstation and specify the location of the image registry for the build output with a registry secret. This buildrun submit command automatically builds and pushes the image to the registry that you specify with the --image option. Specify the --registry-secret option to access your registry.

ibmcloud ce buildrun submit --name buildrun-local-dockerfile2 --source . --image us.icr.io/mynamespace/codeengine-helloworld --registry-secret myregistry

The . indicates the build source is located in your current working directory.



* Code Engine automatically determines whether your source resides in a repo or on a local workstation, based on the value of the --source option.
* In this example, the command uses the default dockerfile strategy, and the default medium build size.



The following table summarizes the options that are used with the buildrun submit command in this example. For more information about the command and its options, see the [ibmcloud ce buildrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-buildrun-submit) command.



Table 6. Command description

 Option Description 

 --name The name of the build run. Use a name that is unique within the project. This value is required.<br><br><br><br> * The name must begin and end with a lowercase letter.<br> * The name must be 63 characters or fewer and can contain lowercase alphanumeric characters and hyphens (-).<br><br><br>
After creating an endpoint gateway for the DNS Services instance, use the service endpoint's 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/instance/<instance-id>/dnszones -H "Authorization: Bearer $iam_token"





 Using the SDK 

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

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



For more examples of setting the service's FQDN for the specific SDK language, see [SDK API examples](https://cloud.ibm.com/apidocs/dns-svcs?code=go).





 Using Terraform 

If you plan to access the DNS Services service using Terraform, make sure to set the IBMCLOUD_PRIVATE_DNS_API_ENDPOINT environment variable to https://api.private.dns-svcs.cloud.ibm.com/v1. For example:

export IBMCLOUD_PRIVATE_DNS_API_ENDPOINT=https://api.private.dns-svcs.cloud.ibm.com/v1

For more information on using Terraform, see [DNS Services resources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-dns-resources) and [DNS Services data sources](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-dns-data-sources).
For details, see [Determining the size of the build](https://cloud.ibm.com/docs/codeengine?topic=codeengine-plan-buildbuild-size). The build size option is allowed if the --build option is not set and not allowed if the --build option is set. This value is optional. The default value is medium.

--source, --src
: The URL of the Git repository or the path to local source that contains your source code; for example https://github.com/IBM/CodeEngine or .. If the --build option is set, the source option is required if the --build-type option on the related build is local and not allowed if the --build-type option on the related build is git. If the --build option is not set, the source option is optional. This value is optional. The default value is ..

--strategy, --str
: The strategy to use for building the image. Valid values are dockerfile and buildpacks. The build strategy option is allowed if the --build option is not set and not allowed if the --build option is set. If not specified, the build strategy is determined by Code Engine if --source is specified and the source is on your local machine. This value is optional. The default value is dockerfile.

--timeout, --to
: The amount of time, in seconds, that can pass before the build run must succeed or fail. This value is optional. The default value is 600.

--wait, -w
: Submit the build run and wait for this build run to complete. If you specify the --wait option, the build run submit waits for a maximum time in seconds, as set by the --wait-timeout option, for the build run to complete. If the build run is not completed within the specified --wait-timeout period, the build run submit fails. This value is optional. The default value is false.

--wait-timeout, --wto