vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 21m
Created: 2021-03-14T14:50:13-05:00

Summary: Succeeded
Status: Succeeded
Reason: Succeeded

For more information about builds, check the [troubleshooting tips](https://cloud.ibm.com/docs/codeengine?topic=codeengine-troubleshoot-build).





 Running a build with the CLI for source from a local directory (local) 

To submit a build run from a build configuration with the CLI that pulls source from a local directory, use the buildrun submit command. This command requires the name of a build configuration, and the path to your local source. Other optional arguments can be specified. For a complete listing of options, see the [ibmcloud ce buildrun submit](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-buildrun-submit) command.

The following scenario clones the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine) into a CodeEngineLocalSample directory on your local workstation.



1. Clone the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine) to a subdirectory that is created on your local workstation, such as the CodeEngineLocalSamples subdirectory. From this directory, run the git clone command; for example,

git clone https://github.com/IBM/CodeEngine
2. Go to the directory where your source code is on your workstation. For example, go to the CodeEngine subdirectory as this is the directory where the Code Engine Samples reside.
3. From the directory where your source code resides, submit the build run.
The API also provides status reasons, with the following codes:<-- <ul> --> * internal_error: Indicates an internal error. Contact IBM support if your see this code. * snapshot_pending: Indicates that backup snapshot in the pendingsnapshot lifecycle state]Snapshot statuses] cannot be deleted. * snapshot_volume_limit: Indicates that the snapshot limit]] ! ! ! ! for the source volume is reached. * source_volume_busy: Indicates that the source volume is busy after multiple retries.<-- </ul> --><-- </section "id="section-backup-jobs-status" "> --><-- </section "class="ph" id="section-backup-view-jobs-api" "> --><-- <section "class="ph" id="section-backup-view-jobs-terraform" "> --> View backup jobs with Terraform To use Terraform, download the Terraform CLI and configure the IBM Cloud Provider plug-in. For more information, see Getting started with Terraform]] ! .VPC infrastructure services use a regional specific based endpoint, which targets to us-south by default. If your VPC is created in another region, make sure to target the right region in the provider block in the provider.tf file.See the following example of targeting a region other than the default us-south. provider "ibm" {
region = "eu-de"
}
<-- <section "id="section-backup-view-jobs-list-terraform" "> --> View a list of backup jobs with Terraform Import the list of a collection of backup jobs as a read-only data source. data "ibm_is_backup_policy_jobs" "example" {
backup_policy_id = ibm_is_backup_policy.example.id
}
For more information about the arguments and attributes, see ibm_is_backup_policy_jobs]ibm_is_backup_policy_jobs] ! !
: The Speech to Text service has migrated to token-based IAM authentication for all locations. All IBM Cloud services now use IAM authentication. The Speech to Text service migrated in each location on the following dates:



* Dallas (us-south): October 30, 2018
* Frankfurt (eu-de): October 30, 2018
* Washington, DC (us-east): June 12, 2018
* Sydney (au-syd): May 15, 2018



The migration to IAM authentication affects new and existing service instances differently:



* All new service instances that you create in any location now use IAM authentication to access the service. You can pass either a bearer token or an API key: Tokens support authenticated requests without embedding service credentials in every call; API keys use HTTP basic authentication. When you use any of the Watson SDKs, you can pass the API key and let the SDK manage the lifecycle of the tokens.
* Existing service instances that you created in a location before the indicated migration date continue to use the {username} and {password} from their previous Cloud Foundry service credentials for authentication until you migrate them to use IAM authentication. For more information about migrating to IAM authentication, see [Migrating Watson services from Cloud Foundry](https://cloud.ibm.com/docs/text-to-speech?topic=watson-migrate).



For more information, see the following documentation:



* To learn which authentication mechanism your service instance uses, view your service credentials by clicking the instance on the [IBM Cloud dashboard](https://cloud.ibm.com/dashboard/apps).
* For more information about using IAM tokens with Watson services, see [Authenticating to Watson services](https://cloud.ibm.com/docs/watson?topic=watson-iam).
* For examples that use IAM authentication, see the [API & SDK reference](https://cloud.ibm.com/apidocs/speech-to-text).







 9 October 2018 

Important updates to pricing charges for speech recognition requests
: As of 1 October 2018, you are now charged for all audio that you pass to the service for speech recognition.
service_endpoint = "https://s3.us-south.cloud-object-storage.appdomain.cloud"

cos = ibm_boto3.resource('s3',
ibm_api_key_id=api_key,
ibm_service_instance_id=service_instance_id,
ibm_auth_endpoint=auth_endpoint,
config=Config(signature_version='oauth'),
endpoint_url=service_endpoint)

response = cos.Bucket('<name-of-bucket>').delete_bucket_lifecycle_configuration(
Bucket='string'
)

print("Bucket lifecyle: {0}".format(response))
Show more

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

package com.ibm.cloud;

import java.sql.Timestamp;
import java.util.List;
import java.util.Arrays;

import com.ibm.cloud.objectstorage.ClientConfiguration;
import com.ibm.cloud.objectstorage.SDKGlobalConfiguration;
import com.ibm.cloud.objectstorage.auth.AWSCredentials;
import com.ibm.cloud.objectstorage.auth.AWSStaticCredentialsProvider;
import com.ibm.cloud.objectstorage.client.builder.AwsClientBuilder.EndpointConfiguration;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
You can see a list of the available runtimes images in the [Available images and runtimes](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-runtimesruntimes_available) section.

Cloud Functions actions can be created by using public images on from Docker Hub.



 Docker skeleton 

You can use the openwhisk/dockerskeleton image to deploy your action. You can use the --native argument as shorthand for --docker openwhisk/dockerskeleton. By using this argument, you can create and deploy an executable that runs inside the standard Docker action SDK.

For more information, see [Creating actions from binaries](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-actionsactions_create_binaries).







 More runtime support 

Go
: By default, all Go actions are executed in a version 1.19 environment. Go Version 1.11, 1.15 and 1.17 are deprecated. When migrating from Go:1.11 to Go:1.17 and higher:



* Go:1.17 uses [Go Modules](https://go.dev/ref/mod).
* File containing the entry function (e.g main.goMain) needs be placed in root, no "main" directory is supported.



: For more information about the go runtimes, see [(Details on GitHub)](https://github.com/apache/openwhisk-runtime-go/blob/master/README.md).
: For more information about writing go actions, see [Preparing Go apps](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-prepprep_go).

Java
: By default, all Java actions are executed in a version 8 environment.
Introduction 

This handbook is intended to serve as a set of standards, styles, and best practices for IBM Cloud SDKs. It is expected to grow and evolve over time in order to best address the needs and requirements of users and developers of IBM Cloud Platform services.

The SDK Handbook is a companion guide to the [IBM Cloud API Handbook](https://cloud.ibm.com/docs/api-handbook?topic=api-handbook-intro), which defines standards, styles, and best practices for IBM Cloud APIs.

To learn how to get involved, see [Contributing](https://cloud.ibm.com/docs/sdk-handbook?topic=sdk-handbook-contributing).
* Some Windows resources in your environment might use classic infrastructure services in Dallas.
* IBM Cloud endpoint service network includes 166.8.0.0/14.
* IBM CloudDriver is an ephemeral VSI that is deployed by the IBM Cloud automation to configure your instance. While IBM CloudDriver is being bootstrapped, it uses an ephemeral primary IP address. However, after bootstrapping it uses a predictable portable IP address that you can find on your instance details page. For more information, see [IBM CloudDriver](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-design_infrastructuremgmtdesign_infrastructuremgmt-cloud-driver).
* Infrastructure VMs refer to the private portable subnet allocated for use by vCenter, NSX manager, the cloud driver
* Depending on your mode of deployment, your Windows Active Directory domain controllers can be VSIs on a primary subnet, or VMs on a portable subnet.



For more information about Red Hat® OpenShift® (OCP) networking, see [About the Red Hat OpenShift SDN network provider](https://docs.openshift.com/container-platform/4.4/networking/openshift_sdn/about-openshift-sdn.html).



Table 1. Ports for deployment and Day 2 operations

 Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 IBM CloudDriver Private primary subnet <br>Infrastructure VMs IBM Cloud Service - Cloud Object Storage <br>10.1.129.0/24<br><br>[1] IBM Cloud infrastructure services network 443 TCP Use IBM Cloud Object Storage service HTTPS 
 IBM CloudDriver Private primary subnet <br>Infrastructure VMs IBM Cloud Service - RabbitMQ 166.9.16.28 <br>166.9.12.34 <br>166.9.14.23 <br>IBM Cloud Service - Log Analysis<br><br>[2] IBM Cloud endpoint service network 443, 30775 TCP Use IBM Cloud RabbitMQ and Log Analysis services
service_endpoint = "https://s3.us-south.cloud-object-storage.appdomain.cloud"

cos = ibm_boto3.resource('s3',
ibm_api_key_id=api_key,
ibm_service_instance_id=service_instance_id,
ibm_auth_endpoint=auth_endpoint,
config=Config(signature_version='oauth'),
endpoint_url=service_endpoint)

response = cos.Bucket('<name-of-bucket>').get_bucket_lifecycle_configuration(
Bucket='string'
)

print("Bucket lifecyle: {0}".format(response))
Show more

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

package com.ibm.cloud;

import java.sql.Timestamp;
import java.util.List;
import java.util.Arrays;

import com.ibm.cloud.objectstorage.ClientConfiguration;
import com.ibm.cloud.objectstorage.SDKGlobalConfiguration;
import com.ibm.cloud.objectstorage.auth.AWSCredentials;
import com.ibm.cloud.objectstorage.auth.AWSStaticCredentialsProvider;
import com.ibm.cloud.objectstorage.client.builder.AwsClientBuilder.EndpointConfiguration;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
ibmAuthEndpoint: 'https://iam.cloud.ibm.com/identity/token',
serviceInstanceId: 'crn:v1:bluemix:public:cloud-object-storage:global:a/<CREDENTIAL_ID_AS_GENERATED>:<SERVICE_ID_AS_GENERATED>::',
};
var s3 = new aws.S3(config);

var params = {
Bucket: 'STRING_VALUE' /* required /
};

s3.getBucketLifecycleConfiguration(params, function(err, data) {
if (err) console.log(err, err.stack); // an error occurred
else console.log(data); // successful response
});

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

package com.ibm.cloud;

import java.sql.Timestamp;
import java.util.List;
import java.util.Arrays;

import com.ibm.cloud.objectstorage.ClientConfiguration;
import com.ibm.cloud.objectstorage.SDKGlobalConfiguration;
import com.ibm.cloud.objectstorage.auth.AWSCredentials;
import com.ibm.cloud.objectstorage.auth.AWSStaticCredentialsProvider;
import com.ibm.cloud.objectstorage.client.builder.AwsClientBuilder.EndpointConfiguration;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
LifecycleConfiguration={
'Rules': [
{
'Status': 'Enabled',
'Filter': {},
'AbortIncompleteMultipartUpload': {
'DaysAfterInitiation': <NUMBER_VALUE>
}
},
]
}
)

print("Bucket lifecyle: {0}".format(response))
Show more

Code sample for use with Java COS SDK

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

package com.ibm.cloud;

import java.sql.Timestamp;
import java.util.List;
import java.util.Arrays;

import com.ibm.cloud.objectstorage.ClientConfiguration;
import com.ibm.cloud.objectstorage.SDKGlobalConfiguration;
import com.ibm.cloud.objectstorage.auth.AWSCredentials;
import com.ibm.cloud.objectstorage.auth.AWSStaticCredentialsProvider;
import com.ibm.cloud.objectstorage.client.builder.AwsClientBuilder.EndpointConfiguration;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
import com.ibm.cloud.objectstorage.services.s3.model.ObjectListing;
import com.ibm.cloud.objectstorage.services.s3.model.S3ObjectSummary;
LifecycleConfiguration={
'Rules': [
{
'Status': 'Enabled',
'Filter': {},
'Expiration':
{
'Days': 123
},
},
]
}
)

print("Bucket lifecyle: {0}".format(response))
Show more

Code sample for use with Java COS SDK

Using the IBM Cloud® Object Storage SDKs only requires calling the appropriate functions with the correct parameters and proper configuration.

package com.ibm.cloud;

import java.sql.Timestamp;
import java.util.List;
import java.util.Arrays;

import com.ibm.cloud.objectstorage.ClientConfiguration;
import com.ibm.cloud.objectstorage.SDKGlobalConfiguration;
import com.ibm.cloud.objectstorage.auth.AWSCredentials;
import com.ibm.cloud.objectstorage.auth.AWSStaticCredentialsProvider;
import com.ibm.cloud.objectstorage.client.builder.AwsClientBuilder.EndpointConfiguration;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3;
import com.ibm.cloud.objectstorage.services.s3.AmazonS3ClientBuilder;
import com.ibm.cloud.objectstorage.services.s3.model.Bucket;
import com.ibm.cloud.objectstorage.services.s3.model.BucketLifecycleConfiguration;
import com.ibm.cloud.objectstorage.services.s3.model.ListObjectsRequest;
import com.ibm.cloud.objectstorage.services.s3.model.ObjectListing;
import com.ibm.cloud.objectstorage.services.s3.model.S3ObjectSummary;
import com.ibm.cloud.objectstorage.oauth.BasicIBMOAuthCredentials;

public class App
{
You can also use the IBM Cloud CLI to create a new service credential (which is a subset of something called a service key). This example extracts the credential and writes it to a file where the IBM COS SDKs can automatically source the API key and Service Instance ID. First, create the Service Key (called config-example and associated with a COS instance called cos-dev-enablement in this example):

ic resource service-key-create config-example --instance-name cos-dev-enablement

Then, extract the credential and create the cos_credential file:

ic resource service-key config-example --output JSON | jq '.[].credentials' > /.bluemix/cos_credentials



 Understanding the endpoints objects 

The endpoints URL (https://control.cloud-object-storage.cloud.ibm.com/v2/endpoints) provided as part of the service credential provides a list of all possible endpoints that can be used when connecting a client:

{
"identity-endpoints":{
"iam-token":"iam.cloud.ibm.com",
"iam-policy":"iampap.cloud.ibm.com"
},
"service-endpoints":{
"cross-region":{
"us":{
"public":{
"us-geo":"s3.us.cloud-object-storage.appdomain.cloud",
"Dallas":"s3.dal.us.cloud-object-storage.appdomain.cloud",
"Washington":"s3.wdc.us.cloud-object-storage.appdomain.cloud",
"San Jose":"s3.sjc.us.cloud-object-storage.appdomain.cloud"
},
"private":{
"us-geo":"s3.private.us.cloud-object-storage.appdomain.cloud",
* [SDK for Node.js](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-getting-started-node)





 Context 

Port secures exchange of port data and shipping manifests that connects public and private organizations.



* Disparate groups of Developers from the government and shipping company don’t have a unified platform where they can collaborate, which slows down deployments of updates and features.
* Developers are spread across the globe and across organizational boundaries, which means open-source and PaaS the best option.
* Security is a primary concern, and this concern increases the collaboration burden that impacts features and updates to the software, especially after the apps are in production.
* Just-in-time data meant that the worldwide systems must be highly available to reduce lags in transit operations. Time tables for shipping terminals are highly controlled and sometimes inflexible. Web usage is growing, so instability might cause poor user experience.







 Solution 

The port and the shipping company co-develop a unified trading system to electronically submit compliance-related information for the clearance of goods and ships once, rather than to multiple agencies. Manifest and customs apps can quickly share contents of a particular shipment and ensure that all paperwork is electronically transferred and processed by agencies for the port.

So they create a partnership that is dedicated to solutions for the trade system.



* DECLARATIONS - App to take in shipping manifests and digitally process typical customs paperwork and to option out-of-policy items for investigation and enforcement
* TARIFFS – App to calculate tariffs, submit charges electronically to shipper, and receive digital payments
* REGULATIONS – Flexible and configurable app that feeds previous two apps with ever-changing policies and regulations that affect imports, exports, and tariff processing



Developers started by deploying their apps in containers with IBM Cloud Kubernetes Service. They created clusters for a shared Dev environment that allow worldwide Developers to collaboratively deploy app improvements quickly. Containers allow each development team to use the language of their choice.

Security first: The IT Execs chose bare metal clusters. With bare metal for IBM Cloud Kubernetes Service, the sensitive customs workloads now have familiar isolation but within the flexibility of public cloud.
Understanding your responsibilities with IBM Cloud Event Notifications 

Learn about the management responsibilities and applicable terms and conditions when you use IBM Cloud Event Notifications. For a high-level view of the service types in IBM Cloud and the breakdown of responsibilities between the customer and IBM for each type, see [Shared responsibilities for IBM Cloud offerings](https://cloud.ibm.com/docs/overview?topic=overview-shared-responsibilities).

Review the following sections for demarcation of responsibilities between you and IBM when you use IBM Cloud Event Notifications. For the overall terms of use, see [IBM Cloud® Terms and Notices](https://cloud.ibm.com/docs/overview/terms-of-use?topic=overview-terms).



 Incident and operations management 

You and IBM share responsibilities for the setup and maintenance of your IBM Cloud Event Notifications instance.

You are responsible for incident and operations management of your application and application data.



Table 1. Responsibilities for incident and operations

 Task IBM Responsibilities Your Responsibilities 

 Incidents Provide notifications for planned maintenance, security bulletins, or unplanned outages. Set preferences to receive emails about platform notifications, and monitor the IBM Cloud status page for general announcements. 







 Change management 

You and IBM share responsibilities for keeping IBM Cloud Event Notifications service components at the latest version.

You are responsible for change management of your application and application data.



Table 2. Responsibilities for change management

 Task IBM Responsibilities Your Responsibilities 

 Applications Provide infrastructure operating system (OS), version, and security updates. Use the API, SDK, CLI, or console tools to apply the provided updates for the local entities (app code, CLI, and SDK). 







 Identity and access management 

You and IBM share responsibilities for controlling access to your IBM Cloud Event Notifications instances and resources.

You are responsible for identity and access management of your application and application data.



Table 3. Responsibilities for identity and access management

 Task IBM Responsibilities Your Responsibilities 

 Applications Offer ability to restrict access to resources. Depending on your needs, restrict access to resources and service functions by using Cloud IAM access policies.
IBMSSEKPCustomerRootKeyCrn: '<root-key-crn>'
}).promise()
.then((() => {
console.log(Bucket: ${bucketName} created!);
logDone();
}))
.catch(logError);
}
Show more

Key Values



* <bucket-location> - Region or location for your bucket (Key Protect is only available in certain regions. Ensure your location matches the Key Protect service) A list of valid provisioning codes for LocationConstraint can be referenced in [the Storage Classes guide](https://cloud.ibm.com/docs/services/cloud-object-storage?topic=cloud-object-storage-classesclasses)..
* <algorithm> - The encryption algorithm used for new objects added to the bucket (Default is AES256).
* <root-key-crn> - CRN of the Root Key that is obtained from the Key Protect service.



SDK References



* [createBucket](https://ibm.github.io/ibm-cos-sdk-js/AWS/S3.htmlcreateBucket-property)









 Using Archive Feature 

Archive Tier allows users to archive stale data and reduce their storage costs. Archival policies (also known as Lifecycle Configurations) are created for buckets and applies to any objects added to the bucket after the policy is created.



 View a bucket's lifecycle configuration 

function getLifecycleConfiguration(bucketName) {
return cos.getBucketLifecycleConfiguration({
Bucket: bucketName
}).promise()
.then((data) => {
if (data != null) {
console.log(Retrieving bucket lifecycle config from: ${bucketName});
console.log(JSON.stringify(data, null, 4));
}
else {
console.log(No lifecycle configuration for ${bucketName});
}
})
.catch((e) => {