vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* [Setting an access policy for your Cloud Functions service ID through the CLI](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-iamcli-set)









 Integrating serverless apps 

[Binding IBM Cloud services to Cloud Functions entities](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-servicesservices)



* [Binding a service to an action or package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-servicesservices_bind)
* [Binding Cloud Foundry based services](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-servicesservices_bind_cf)
* [Unbinding services from actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-servicesservices_unbind)



[Incorporating packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ovpkg_ov)



* [Overview for packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ovpkg_overview)
* [Browsing pre-installed packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ovpkg_browse)
* [Binding parameters to pre-installed packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ovpkg_bind)
* [Adding your own packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_ovpkg_add)
Setting spending notifications 

If you have an IBM Cloud® Pay-As-You-Go or Subscription account, you can set up email spending notifications. Now, in addition to account owners, any user on the account with the editor role or higher on the billing service can set spending notifications. You can enable spending notifications for total account, Cloud Foundry runtime, container, and service spending, or add spending for individual services, including third-party services.

You receive notifications when you reach 80%, 90%, and 100% of the spending thresholds that you specify. As your needs change, you can edit the spending threshold. If you're interested, you can use our latest enhancement to select up to 10 users from your account to receive notifications about the service.

Lite accounts can't enable spending notifications because they can use only no-cost services, so you never have any spending. After you upgrade to a Pay-As-You-Go or Subscription account, you can set spending thresholds. For more information, see [Account types](https://cloud.ibm.com/docs/account?topic=account-accounts).

To set up your notifications:



1. In the IBM Cloud® console, go to Manage > Billing and usage, and select Spending notifications.
2. Set the Enable option to on for the specific service area to enable email notifications.
3. Click the Edit option from the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/icons/action-menu-icon.svg) menu.
4. Next, you can add email recipients. You can select up to 10 users from your account to receive email notifications about a service.
5. Enter the dollar amount to set a spending threshold.
6. When you are finished, click Save to save your changes.



You can also set spending notifications for individual services:



1. From the console, go to Manage > Billing and usage, and select Spending notifications.
With the BYOL pricing model, IBM Cloud doesn't charge users for the usage of the software, and third-party providers are responsible for licensing entitlement and enforcement.

For the purposes of this tutorial, complete the following steps to add a BYOL pricing plan.



1. Click Pricing > Pricing plans.
2. Click Add plan > BYOL.
3. Enter the name, URL, and description of the license, for example:



* Name: BYOL for Example Corp Node-RED Operator 1.0.0
* URL: byol.operator.examplecorp.html
* Description: This BYOL license is required for the installation and use of the Example Corp Node-RED Operator.









 Step 5: Define your support experience 

Provide details that help users understand how to get support if they encounter issues when they use the Operator bundle. For more information about providing support information, see [Defining your support experience](https://cloud.ibm.com/docs/sell?topic=sell-sw-support-details).

To define your product's support experience, use the following steps:



1. Click Support.
2. Select your product's support provider and complete the support statement field. For the support statement, describe the provided support for your product and add any additional support information that isn't provided in the other fields.



1. If you select Community for your support provider, provide the URL for the support community.
2. If you select Third-party for your support provider, use the following steps to complete the necessary fields.



3. Click Add support details and complete the necessary fields, then click Save to add each detail. You must add at least 1 support detail for your product.
4. After you add all of your product's support details, provide the required URLs for your product.
5. Add all locations where you provide support for your product.
6. Add your escalation information. Do not use a personal phone number or email.
7. Provide your support contact information. This information is for internal use only and is not displayed on the product details page.







 Next steps
Details of specific third-party service integrations can be found in the [External Service Integrations](https://cloud.ibm.com/docs/services/IoT?topic=IoT-ref-indexref-index) topic.



 How the Watson IoT Platform works with IBM Cloud 

Instances of the Watson IoT Platform can be created in the IBM Cloud dashboard. The Watson IoT Platform can be integrated with other IBM Cloud services and accessed by using the IBM Cloud dashboard, however, Watson IoT Platform does not run on IBM Cloud hardware, which allows for continual data collection by your Watson IoT Platform service.





 Watson IoT Platform service level agreement 

The Watson IoT Platform has provisions for a specified level of service. For details of the service level agreement, see [Watson IoT Platform service level agreement ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://cloud.ibm.com/docs/overview?topic=overview-zero-downtimeSLAs).





 IBM Cloud service level agreement 

IBM Cloud publishes terms of use, which differ depending on whether the [IBM Cloud Services Agreement ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](http://www-05.ibm.com/support/operations/files/pdf/csa_us.pdf?cm_mc_uid=65870113399114371461368&cm_mc_sid_50200000=1469524513) or the [IBM International Passport Advantage Agreement ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://www.ibm.com/software/passportadvantage/pa_agreements.html) apply to the user.





 Watson IoT Platform Pricing 



 IoT Pricing Calculator 

For more information on the available Watson IoT Platform plans and pricing models:



1.
They can continue to work in their Premium instances and create instances up to the 30-instance limit. New users do not see the Premium plan as an option when they create a service instance.

For more information, see the [Pricing](https://www.ibm.com/cloud/watson-assistant/pricing/) page.

Other plan changes
: Our pricing has been revised to reflect the features we've added that help you build an assistant that functions as a powerful omnichannel SaaS application.

Starting on 1 March 2021, the Plus plan starts at $140 per month and includes your first 1,000 monthly users. You pay $14 for each additional 100 active users per month. Use of the voice capabilities that are provided by the Phone integration are available for an additional $9 per 100 users per month.

The Plus Trial plan was renamed to Trial.

SOC 2 compliance
: Watson Assistant is SOC 2 Type 2 compliant, so you know your data is secure.

The System and Organization Controls framework, developed by the American Institute of Certified Public Accountants (AICPA), is a standard for controls that protect information stored in the cloud. SOC 2 reports provide details about the nature of internal controls that are implemented to protect customer-owned data. For more information, see [IBM Cloud compliance programs](https://www.ibm.com/cloud/compliance/global).





 25 February 2021 

Search skill can emphasize the answer
: You can configure the search skill to highlight text in the search result passage that Discovery determines to be the exact answer to the customer's question. For more information, see [Creating a search skill](https://cloud.ibm.com/docs/assistant?topic=assistant-skill-search-add).

Integration changes
: The following changes were made to the integrations:



* The name of Preview link integration changed to Preview.
* The Web chat and Preview integrations are no longer added automatically to every new assistant.

The integrations continue to be added to the My first assistant that is generated for you automatically when you first create a new service instance.



Message and log webhooks are generally available
IBM Cloud Kubernetes Service integrates popular open source integrations, such as [Istio](https://cloud.ibm.com/docs/containers?topic=containers-istio) by using [managed add-ons](https://cloud.ibm.com/docs/containers?topic=containers-managed-addons). Managed add-ons are an easy way to install an open source tool in your cluster that is tested by IBM and approved to be used in IBM Cloud Kubernetes Service.

Managed add-ons are fully integrated into the IBM Cloud support organization. If you have a question or an issue with using the managed add-ons, you can use one of the IBM Cloud Kubernetes Service support channels. For more information, see [Getting help and support](https://cloud.ibm.com/docs/containers?topic=containers-get-help).

If the tool that you add to your cluster incurs costs, these costs are automatically integrated and listed as part of your monthly IBM Cloud billing. The billing cycle is determined by IBM Cloud depending on when you enabled the add-on in your cluster.





 Other third-party integrations 

You can install any third-party open source tool that integrates with Kubernetes. For example, the Kubernetes community designates certain Helm charts stable or incubator. Note that these charts or tools are not verified to work in IBM Cloud Kubernetes Service. If the tool requires a license, you must purchase a license before you use the tool. For an overview of available Helm charts from the Kubernetes community, see the kubernetes and kubernetes-incubator repositories in the [Helm charts](https://cloud.ibm.com/kubernetes/helm) catalog.

Any costs that incur by using a third-party open source integration are not included in your monthly IBM Cloud bill.

Installing third-party open source integrations or Helm charts from the Kubernetes community might change the default cluster configuration and can bring your cluster into an unsupported state. If you run into an issue with using any of these tools, consult the Kubernetes community or the service provider directly.
* UI
* API







 Connecting services to external apps 

You might have applications that were created and run outside of IBM Cloud®, or you might use third-party tools. If IBM Cloud services provide service keys that are accessible from the internet, you can use those services with your local apps or third-party tools.

To enable an external app or third-party tool to use an IBM Cloud service, complete the following steps:

Most services don't require extra parameters, and for services that do, each service defines its own unique list of parameters. For a list of supported configuration parameters, see the documentation for the particular service.



 Connect a service to an external app in the console 



1. Create an instance of the service.



1. Click Catalog.
2. From the catalog, select the service that you want by clicking the service tile.
3. Select the location and org and space or resource group, and then click Create.



2. From the service details page, select Service Credentials to view or add credentials in JSON format.



* To create new credentials, select New credential and optionally add configuration parameters manually or import a file in JSON format, then click Add. Select View credentials to save the credentials to connect to your external app.
* Select a set of credentials and click View credentials in the Actions column if they already exist.



3. Use the API key that is displayed as the credentials to connect to the service instance.



Your application that runs outside of IBM Cloud can now access the IBM Cloud service.

If you want to delete service instances or check the billing information, you must go back to the Resource list page in the user interface to manage the service instances.





 Connect a service to an external app by using the API 



1. Create an instance of the service by calling [Resource Controller API](https://cloud.ibm.com/apidocs/resource-controller/resource-controller?code=gocreate-resource-instance) as shown in the following example request:



* Curl
* Java
* Python
* Go
* Node
For example, consider a runtime that costs $0.07 per GB-hour in two 512-MB instances, running for 30 days (720 hours). These resources would cost $50.4 USD, with the following calculations:

2 instances x 0.5 GB x 720 hours = 720 GB-hours.
720 GB-hours x $0.07 per GB-hour = $50.4





 Charges for services 

Many services include monthly free allowances. Usage of services that aren't included as part of the free allowance is charged in one of the following ways:

Fixed charges
: You select a plan and pay on a flat rate basis. For example, the Bare Metal Servers are charged at a flat-rate.

Metered charges
: You pay based on your runtime and service consumption. For example, with the Push service, any usage over the free monthly allowance is charged.

Reserved charges
: As the account owner of a Pay As You Go account or a Subscription account, you can reserve a service instance, with a long-term commitment, for a discounted price. For example, you can reserve the standard large Db2 on Cloud offering for 12 months.
: Some IBM Cloud services offer reserved plans. You can request a reserved plan from the IBM Cloud catalog by clicking the tile of the service. Then, select the service plan that best meets your needs. If a reserved plan is available, click Request, and follow the prompts to send your request. You receive an email that contains the price information of the reserved plan. An IBM Cloud sales representative also contacts you soon to complete the purchase.

Tiered charges
: Similar to metered charges, you pay based on your runtime and service consumption. However, tiered charges add more pricing tiers, often offering discounted charges in tiers with larger consumption. Tiered pricing is offered in simple, graduated, or block.



 Simple tier 

In the simple tier model, the unit price is determined by the tier that the quantity of your usage falls into. The total price is your quantity that is multiplied by the unit price in that tier, for example:



Table 2. Simple tier pricing table

 Quantity of Items Unit Price for All Items
https://us-south.functions.cloud.ibm.com/api/v1/web/my_org_dev/default/translateToEnglish.json

You must specify a URL that uses the SSL protocol, so specify a URL that begins with https.

You cannot use a webhook to call a Cloud Functions action that uses token-based Identity and Access Management (IAM) authentication. However, you can make a call to a Cloud Functions web action or a secured web action.
6. In the Secret field, add a private key to pass with the request that can be used to authenticate with the external service.

The key must be specified as a text string, such as purple unicorn. Maximum length is 1,024 characters. You cannot specify a context variable.

It is the responsibility of the external service to check for and verify the secret. If the external service does not require a token, specify any string you want. You cannot leave this field empty.

For more information about how this field is used, see [Webhook security](https://cloud.ibm.com/docs/assistant-data?topic=assistant-data-webhook-prewebhook-pre-security).
7. In the Headers section, add any headers that you want to pass to the service one at a time by clicking Add header.

For example, if the external application that you call returns a response, it might be able to send a response in multiple different formats. The webhook requires that the response is formatted in JSON. The following table illustrates how to add a header that indicates that you want the resulting value to be returned in JSON format.



Header example

 Header name Header value 

 Content-Type application/json 



The service automatically sends an Authorization header with a JWT; you do not need to add one. If you want to handle authorization yourself, add your own authorization header and it will be used instead.



Your webhook details are saved automatically.





 Testing the webhook 

Do extensive testing of your webhook before you enable it for an assistant that is being used in a production environment.
* IBM Cloud Direct Link requires you to use a VRF (Virtual Routing and Forwarding) instance.
* VRF isn't fully compatible with the IBM Cloud SSL and IPsec VPN services.
* The IBM Cloud fees for Direct Link Dedicated cover the cost of port termination on the IBM Cloud infrastructure. Customers are responsible for any fees that are associated with reaching the PoP from a remote network and any cross-connects needed within the PoP facility. IBM Cloud does not order a cross-connect on any customer's behalf.
* IBM Cloud does not colocate any customer equipment in our network PoPs. Customers must work with their provider to determine whether they need to colocate any equipment in the facility where the IBM Cloud network PoP exists.
* Direct Link Dedicated is a switchport in access mode. Currently, 802.1q is not supported.
Add a pricing plan for your service 

This tutorial walks you through the steps for adding pricing plans and features for your third-party service. By completing this tutorial, you submit required documentation, add your Export Control Classification Number (ECCN) and United Nations Standard Products and Services Code (UNSPSC), define your pricing plan, and add a list of features for your product.

This tutorial is one of five in a series that demonstrates how to onboard and publish a service to the IBM Cloud catalog. As you complete the tutorial, adjust each step to fit your needs.



 Before you begin 



1. [Register your service in IBM Cloud Partner Center](https://cloud.ibm.com/docs/sell?topic=sell-svc-register).
2. [Define the product details of your service](https://cloud.ibm.com/docs/sell?topic=sell-svc-define).
3. [Onboard a broker](https://cloud.ibm.com/docs/sell?topic=sell-broker-onboard).







 Step 1: Submit required documentation 

As part of this tutorial, you add a usage-based pricing plan. To receive disbursements for usage-based pricing plans, you must submit the Electronic Funds Transfer (EFT) form and required tax document.

To provide tax and EFT information, complete the following steps:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > Payments to me.
2. Download the relevant EFT form, and complete it.

A scanned copy of a voided check is required when you submit this form.
3. Download the relevant tax documentation, and complete it.
4. Submit the completed documentation by email to apremit@us.ibm.com. You must include cloud.onboarding@ibm.com on the email.
For server-side entities like microservices, when the state of a feature flag or property changes in the App Configuration, a websocket connection notifies the SDK in the microservice that a state change occurred. The microservice then calls back into the App Configuration to retrieve the update. This action is an API call.

An API call also occurs on startup to the retrieve the initial configuration state. For client-side entities like mobile apps, websockets are not used. Instead, an API call fetches the current configuration state when a user opens the app, or brings it to the foreground. You can also programmatically call the App Configuration to retrieve the most recent configuration state.





 How to view usage metrics for App Configuration? 

View basic historical App Configuration usage metrics on the IBM platform [Billing and Usage dashboard](https://cloud.ibm.com/billing/usage). If you need more sophisticated monitoring, create an IBM Cloud Monitoring instance from the [Observability](https://cloud.ibm.com/observe) section of the IBM Cloud console.





 How to predict App Configuration cost? 

The simplest way to estimate cost for any IBM Cloud managed service is to use the [IBM Cloud Cost Estimator tool](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-cost).

Guidelines to help you predict cost in more detail:

The Application Instance cost is a fixed monthly cost. If you delete an App Configuration instance mid-month, the monthly Application Instance charge is pro-rated. To predict month instance cost, you must be aware of the number of App Configuration instances you have and what pricing plan is assigned to each.

See all your existing instances in the IBM Cloud Console Resource List in the Services Section. Determine your plan either by clicking the Resource List row that contains your App Configuration instance to reveal an information slide-out, or go to the instance dashboard and look in the Plan section.

Some App Configuration pricing plans have a monthly Application Instance price and others do not. If the plan you select has an instance price, the price for the instance includes a set number of entity IDs and API calls that are included in the instance price.
Whether you have an app already or plan to develop a script to use, your code probably needs a few tweaks to make it consumable by IBM Cloud® Functions. The code itself must meet some structural requirements, such as the input parameters and the output results. It might also need to be packaged into a single file that includes all its dependencies.







 Determine your event source 

Think about your function in terms of the event you want to happen to trigger code to run. Maybe you want code to run on every commit to a GitHub repository. Or maybe you want your code to run every time that an update is made in a Cloudant database.

After you choose an event to trigger your function, review the packages that are already available to use. You might be able to use one to simplify your function development. If not, you can create your own package for your event source.

You might need to go back to your code and make some revisions based on your event selections.





 Organize deployments across environments 

Decide how you want to deploy your functions across environments, such as development, staging, and production environments.

Because Cloud Functions is a Cloud Foundry-based service, you can manage the deployment of your functions in the Cloud Foundry organizations and spaces that are provided for you in IBM Cloud. To organize your functions across these environments, you might choose to create one organization per function. Then, create a space for each environment you need. Instead, you could also have one organization for each environment and create a space per function. No matter how you arrange your organizations and spaces, choose a structure that you can use to effectively manage your function entities.

You can also use [namespaces](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-namespaces) to isolate resources. Each IBM Cloud space contains an Open Whisk namespace by default. You can group entities, such as actions or triggers in a namespace, and then create Identity and Access (IAM) policies to manage user permissions for that group.