vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Getting started with App Configuration 

IBM Cloud® App Configuration is a centralized feature management and configuration service for use with web and mobile applications, microservices, and distributed environments. Instrument your applications with App Configuration SDKs, and use the App Configuration dashboard or App Configuration administrator API to define features flags or properties, which are organized into collections and targeted to segments. Change feature flag states in the cloud to activate or deactivate features in your application or environment, often without restarting. You can also manage the properties for distributed applications centrally.

App Configuration currently offers three pricing [plans](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-faqs-usagefaq-ac-pricing): Lite, Standard, and Enterprise.

You need an IBM Cloud® account. If you don't have an account, create one [here](https://cloud.ibm.com/registration/). Log in to your IBM Cloud account.

The basic steps that get you started:



1. [Create an App Configuration service instance](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-create-an-instance)
2. [Create a collection](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-collectionsac-create-a-collection)
3. [Set up environments, feature flags, and properties](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-ff-prop-env)
4. [Integrate App Configuration service SDKs](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-integrate-sdks)
5. [Create segments](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-segmentsac-create-segment)
6.
Check out the new [tutorial series](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-tutorial-expiring-secrets-part-1) that guides you through:



* Enabling [Event Notifications](https://cloud.ibm.com/docs/event-notifications) for Secrets Manager
* Using [Cloud Functions](https://cloud.ibm.com/docs/openwhisk) to create a GitHub issue when a secret is about to expire
* Using Cloud functions to sending a notification to Slack







 28 February 2022 

Sao Paulo availability
: You can now create a Secrets Manager service instance in the Sao Paulo (br-sao) region.

For more information, see [Regions and endpoints](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-endpoints).





 23 February 2022 

Pricing plan updates coming soon in Secrets Manager
: On 23 March 2022, Secrets Manager will introduce Standard and Trial pricing plans. With the introduction of the new plans, the current Lite plan option is deprecated.

Types of plans:

When you provision an instance of the service after the 23 March, you can choose either a Trial or Standard plan.



* Trial: To try out the service, you can provision an instance of the service to access all the features that Secrets Manager offers for a limited time. After the trial period, all functionality is disabled but the instance remains in your account for an additional 30 days, during which you can choose to upgrade your plan. If you choose not to, the instance and its data are automatically removed from your account without any action on your part.



You can have one instance of the service on the trial plan that is provisioned in your account at any time.



* Standard: When you're ready to upgrade, you get unlimited access to all the features that the service offers. The number of instances that your teams can provision is unlimited. With the Standard plan, you are charged per secret and per instance that is provisioned. To view the most current pricing information, see the Secrets Manager UI.



Important dates:

Be sure to keep the following dates in mind:
Node 

As one of the most popular programming languages in use today, JavaScript support is imperative to increase adoption of your IBM Cloud service. The great strength of JavaScript is its flexibility; it can be used in backend [Node.js](https://nodejs.org/) applications, as well as in client side frameworks like [React](https://reactjs.org/), [Angular](https://angularjs.org/) and [Vue](https://vuejs.org/), among others. This introduces special considerations that need to be observed in order to meet the needs of these diverse use cases.



 TypeScript 

Your JavaScript library should be written in [TypeScript](https://www.typescriptlang.org/). This will allow TypeScript applications and JavaScript alike to use your SDK.





 Environment support 



* All [LTS versions](https://nodejs.org/en/about/releases/) of Node should be supported by your SDK.
* Your SDK should support all TypeScript releases above 3.1.
* All modern browsers should be supported by your SDK.
* Ensure your SDK is compatible with React, Angular, and Vue.







 Publishing 

All Node SDKs should be publicly available on an [IBM GitHub organization](https://cloud.ibm.com/docs/sdk-handbook?topic=sdk-handbook-distributiondistribution-opensrc). The releases of these SDKs should be published on [NPM](https://www.npmjs.com/). Your NPM package should be [scoped](https://docs.npmjs.com/creating-and-publishing-scoped-public-packagescreating-a-scoped-public-package) with [@ibm-cloud](https://www.npmjs.com/search?q=%40ibm-cloud), so that NPM users can find similar packages across NPM.
[Elements of pricing](https://cloud.ibm.com/docs-content/v1/content/c5288bed34c3820e3a5251d820ee91adcd2591a3/blockchain/images/elements-of-pricing.svg)

Figure 1. Elements of pricing



* IBM Blockchain Platform: Based on a flat rate of $0.29 USD/VPC-hour. This fee represents the charge for your blockchain component VPC allocation in your Kubernetes cluster.
* IBM Cloud Kubernetes Service: While you can link your IBM Blockchain Platform service instance to either an IBM Cloud Kubernetes service cluster or an OpenShift cluster, this pricing model is based on the usage of an IBM Cloud Kubernetes service cluster. The IBM Cloud Kubernetes service uses a tiered pricing model that is visible in IBM Cloud when you provision your paid cluster. This includes the charges for your compute, that is, CPU and memory. IBM Cloud Kubernetes Services are priced on a tiered model that is based on the number of hours of usage per month. Therefore, when you examine pricing plans, consider that 24x7 usage is equivalent to 720 hours per month. Refer to the table on the [Kubernetes Service Catalog page](https://cloud.ibm.com/kubernetes/catalog/about) for more details on cluster pricing. Customers who are interested in pricing OpenShift clusters can review [Red Hat OpenShift on IBM Cloud Pricing](https://www.ibm.com/cloud/openshift/pricing).
* Storage: Choose the storage plan that works for your needs. See [Understanding Kubernetes storage basics](https://cloud.ibm.com/docs/containers?topic=containers-kube_conceptskube_concepts) to learn more about your storage class options and how much they [cost](https://www.ibm.com/cloud/file-storage/pricing). The IBM Blockchain Platform nodes use the default storage class for the cluster.
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. If you exceed the included allotment, your instance continues to operate normally but you accumulate an overage charge based on the published rate for entity IDs and API calls.

The Active Entity ID cost is based on the number of unique entities that interact with your App Configuration instance during the month. Entities self-identify when an API call is made, and each instance of your application provides a unique entity ID. You are not charged for entities that do not call App Configuration during the month. If your pricing plan includes a free allotment of Active Entity IDs, then you are not charged until the allotment is exceeded.

Active Entity ID cost can be difficult to predict so you need to closely monitor your historical activity. See [How to view usage metrics for App Configuration?](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-faqs-usagefaq-ac-metrics) Rely on your own domain knowledge, business metrics, and usage forecasts to predict Active Entity ID cost.

The API Call cost is based on the number of API calls sent or received by App Configuration during the month over all your entities combined. Check section - [What are the charges to use App Configuration?](https://cloud.ibm.com/docs/app-configuration?topic=app-configuration-ac-faqs-usagefaq-ac-charges) to determine what constitutes an API call.

If your pricing plan includes a free allotment of API calls, then you are not charged until the allotment is exceeded. Closely monitor your historical activity and check out [How to view usage metrics for App Configuration?]
Cloud Functions and API Connect
: When you create your APIs with [Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-getting-started) and [API Connect](https://cloud.ibm.com/docs/apiconnect?topic=apiconnect-getting-started), you can secure your applications at the gateway rather than in your app code.

Activity Tracker
: You can monitor administrative activity that is made in App ID such as changes to the dashboard configuration, by using the [Activity Tracker service](https://cloud.ibm.com/docs/activity-tracker?topic=activity-tracker-getting-started).





 Standards and certifications 

App ID has successfully completed several certifications, audits, and standards.

App ID is based on a set of well-known, industry standard protocols and specifications that are frequently found in both enterprise and consumer facing applications, the OAuth 2.0 Authorization Framework and Open ID Connect. OAuth 2.0 is used to obtain and verify authorization for accessing protected resources. Open ID Connect then adds a layer of authentication and identity protection to your application.

See section 5.4 of the App ID software product compatibility report to review a complete list of [certifications](https://www.ibm.com/software/reports/compatibility/clarity-reports/report/html/softwareReqsForProduct?deliverableId=BF31C8008D7C11E59F9AD7336D7D0FFB). In addition to the certifications, App ID is also compliant in the following specifications: OAuth 2.0, OpenID Connect, JSON Web Token (JWT), JSON Web Signature (JWS), System for Cross-domain Identity Management (SCIM).
Installation of Cloud Pak for Integration on IBM Cloud using the IBM software catalog does not support MZR clusters. See [Known limitations](https://cloud.ibm.com/docs/cloud-pak-integrationknown-limitations) for more details.





 Step 1. Obtain a license 

If you don't already have a license, you can:



* Purchase a license through [IBM Passport Advantage](https://www.ibm.com/software/passportadvantage/index.html)
* [Register](https://www.ibm.com/account/reg/signup?formid=urx-46640) for a 60-day trial license of IBM Cloud Pak for Integration

Important: The trial is for IBM Cloud Pak for Integration software only. The trial does not include entitlement to the Red Hat OpenShift Container Platform.







 Step 2. Assign a license 

To assign your license, follow these steps:



1. Sign up to, or log in to your [IBM Cloud account](https://cloud.ibm.com/login).
2. Navigate to Manage > Account and then click Licenses and entitlements in the navigation menu.
3. If there are no licenses to assign on the Licenses and entitlements page, click Check IBM Passport Advantage.
4. Select the appropriate license and click Assign.







 Step 3. Select your cluster 

Open [Cloud Pak for Integration from the IBM Cloud Catalog](https://cloud.ibm.com/catalog/content/ibm-cp-integration).

Select the target OpenShift Cluster. You can filter the table by entering the name of the cluster created in the Before you Begin step in the search field.

In the Project field, select from an existing project or create a new one by entering a unique project name. A project is a Kubernetes cluster namespace, and the list is populated from your Red Hat OpenShift environment. This project name is used as the namespace for the Platform Navigator.





 Step 4. Configure your schematics workspace
For more information, see [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).





 Step 1: Create an application 

Create an application to receive your GitHub events called my-github-app that uses an image called github with the [ibmcloud ce app create](https://cloud.ibm.com/docs/codeengine?topic=codeengine-clicli-application-create) command. This app logs each commit event that occurs in the GitHub repository. The image is built from github.go, available from the [Samples for IBM Cloud Code Engine GitHub repo](https://github.com/IBM/CodeEngine/tree/main/github).

ibmcloud ce application create --name my-github-app --image icr.io/codeengine/github --min-scale 1

After your application creates, verify that your application is in a Ready state and find the application URL.

ibmcloud ce application get --name my-github-app

The application URL is found in the URL field in the example output.

Name: my-github-app
ID: abcdefgh-abcd-abcd-abcd-1a2b3c4d5e6f
Project Name: myproject
Project ID: 01234567-abcd-abcd-abcd-abcdabcd1111
Age: 20h
Created: 2022-11-28T13:16:49-06:00
URL: https://my-github-app.abcdabcdabc.us-south.codeengine.appdomain.cloud
Cluster Local URL: http://my-github-app.abcdabcdabc.svc.cluster.local
Running a function from local source 

With this tutorial, run a Function with the Code Engine CLI from code on your local system

A Function is a stateless code snippet that performs tasks in response to an HTTP request. With IBM Code Engine Functions, you can run your business logic in a scalable and serverless way. IBM Code Engine Functions provide an optimized runtime environment to support low latency and rapid scale-out scenarios. Your Function code can be written in in Node.js or Python, which are optimized to run in IBM Code Engine Functions. In addition, your Function code can be written for any OpenWhisk compatible runtime environment or a custom runtime image.

Before you begin



* [Set up your Code Engine CLI environment](https://cloud.ibm.com/docs/codeengine?topic=codeengine-install-cli).
* [Create and work with a project](https://cloud.ibm.com/docs/codeengine?topic=codeengine-manage-project).



All Code Engine users are required to have a Pay-as-you-Go account. Tutorials might incur costs. Use the Cost Estimator to generate a cost estimate based on your projected usage. For more information, see [Code Engine pricing](https://cloud.ibm.com/docs/codeengine?topic=codeengine-pricing).



 Step 1: Set up your environment 



1. Log in to the IBM Cloud CLI.

ibmcloud login -r us-south
2. Target a resource group by running the following command. To see a list of your resource groups, run ibmcloud resource groups.

ibmcloud target -g <resource_group>

Example output

Targeted resource group default
3. Create a project in Code Engine called sample.

ibmcloud ce project create --name sample

Example output

Creating project 'sample'...
ID for project 'sample' is 'abcdabcd-abcd-abcd-abcd-abcd12e3456f7'.
The offering supports the Bring Your Own License (BYOL) model for [IBM Spectrum Symphony](https://www.ibm.com/products/analytics-workload-management) and [IBM Spectrum Scale](https://www.ibm.com/products/spectrum-scale/pricing) to deploy an HPC cluster on IBM Cloud. Make sure that you have sufficient software licenses to deploy the required capacity on the IBM Cloud cluster. For evaluation purposes, IBM Cloud does enable limited access. Contact your IBM Cloud sales or support team for evaluation licenses.

IBM Spectrum Symphony allows use of three interfaces: UI, API, and CLI. One UI option is the [IBM Cloud catalog tile](https://cloud.ibm.com/catalog/content/terraform-1627942334-78300480-b376-4185-9812-b7ae00d82765-global). [Schematics](https://www.ibm.com/cloud/schematics) also offers a UI, as well as API and CLI interfaces, and the Terraform-based automation code for use with Schematics is available in this [public GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-symphony).

The offering enables initial Spectrum Symphony-based HPC cluster creation. Any updates that are needed post-deployment regarding Spectrum Symphony or Spectrum Scale configuration or setup should be performed by using Symphony and Scale tools and commands. If you use the Schematics interfaces to make changes to configuration properties and reapply those changes, you can cause disruptions to the running IBM Spectrum Symphony cluster. Restoring it back to a working state might not be easy.



 Architecture diagram 

The following diagram depicts a Spectrum Symphony cluster that uses NFS for shared storage. For a view of a cluster that uses Spectrum Scale, see the [Using Spectrum Scale storage](https://cloud.ibm.com/docs/hpc-spectrum-symphony?topic=hpc-spectrum-symphony-using-spectrum-scale-storage) section.

Zoom

!
[A view of the invoices page in the IBM Cloud console. This view displays new and one-time charges that reflect what you're charged.](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/billing-usage/images/example-invoice-console.png)

Figure 3. New and one-time charges in the console for the month of March.

The remaining infrastructure charges of $322,806.71 USD from the recurring invoice in the console and the new and one-time charges should add up to the total IaaS final invoice charge of $324,245.93 USD.





 Granular view of the line item charges 

Now that we confirmed that the final invoice totals match the recurring and new and one time charges in the console, let’s find out what the charges on the final invoice represent.

On the Excel version of your recurring invoice that you downloaded in step 2, click the Detailed Billing tab. The Detailed Billing tab provides a breakdown of all of your infrastructure and platform charges. They represent three major types of usage:



* In Advance (for example, the month of March) infrastructure monthly usage charges. These are recurring charges that you incur until you cancel the service. The charge is the same every month.



Zoom

![An example of an advanced infrastructure monthly usage charges on the detailed invoice tab from the downloaded Excel invoice.](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/billing-usage/images/advance-billing.png)

Figure 4. In advance infrastructure monthly usage charges.



* In Arrears (for example, the month of February) infrastructure hourly charges. These are usage-based charges from the previous month. Note the 672 hrs * .066 format of the charges.
You go through this process only one time.<br><br>If you have problems when you associate your IBMid with an IBM Cloud account, see [Why is my password incorrect?](https://cloud.ibm.com/docs/account?topic=account-ts_logintoibm) 
 IBM Cloud account To order and use IBM Cloud services, an IBM Cloud account is required. Billing information is associated with the IBM Cloud account. The price of the physical and virtual infrastructure and the resulting licenses are charged to your IBM Cloud account. 
 IBM Cloud infrastructure account For more information, see [The IBM Cloud infrastructure account](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accountssigning_required_accounts-infra).<br><br>You can link IBM Cloud infrastructure accounts with IBM Cloud accounts to use combined infrastructure as a service (IaaS) and platform as a service (PaaS) resources. Then, you can access IaaS resources and PaaS resources from a single login. Linking your accounts also provides you with a single invoice for all the PaaS and IaaS resources that you use.<br><br>If you do not have an IBM Cloud infrastructure account, request one by following the procedure in [Signing up for an IBM Cloud infrastructure account](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-signing_required_accountssigning_required_accounts-infra), and then link your IBM Cloud infrastructure account with your IBM Cloud account by following the procedure in [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account).<br><br>If you have an IBM Cloud infrastructure account, you can link it with your IBM Cloud account by following the procedure in [Upgrading your account](https://cloud.ibm.com/docs/account?topic=account-upgrading-account). 







 Deployment offerings 

Review and choose your deployment offering.



Table 2. Deployment offerings

 Deployment offering Description
You can also [apply your promo code](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-applying-promo-codes) if you have one. For more information about IBM Cloud accounts, see [FAQs for accounts](https://cloud.ibm.com/docs/account?topic=account-accountfaqs).

The service can be provisioned quickly by following instructions in [Provisioning service instances](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-provision). However, in order to perform key management and cryptographic operations, you need to [initialize service instances](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-instance-mode) first by using IBM Cloud TKE CLI plug-in or the Management Utilities.
* How to initialize Hyper Protect Crypto Services service instances?

To initialize the service instance, you need to create administrator signature keys, exit the imprint mode, and load the master key to the instance. To meet various security requirements of your enterprises, IBM offers you the following options to load the master key:



* [Using the IBM Hyper Protect Crypto Services Management Utilities](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-management-utilities) for the highest level of security. This solution uses smart cards to store signature keys and master key parts. Signature keys and master key parts never appear in the clear outside the smart card.
* Using the IBM Cloud TKE CLI plug-in for a solution that does not require the procurement of smart card readers and smart cards. This solution supports two approaches to initializing service instances: [by using recovery crypto units](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm-recovery-crypto-unit) and [by using key part files](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-initialize-hsm).