vania-janet/multiturn-rag-retrieval-data huggingface dataset:
options := iamPolicyManagementService.NewCreatePolicyOptions(
"access",
[]iampolicymanagementv1.PolicySubject{policySubjects},
[]iampolicymanagementv1.PolicyRole{policyRoles},
[]iampolicymanagementv1.PolicyResource{policyResources},
)

policy, response, err := iamPolicyManagementService.CreatePolicy(options)
if err != nil {
panic(err)
}
b, _ := json.MarshalIndent(policy, "", " ")
fmt.Println(string(b))

const policySubjects = [
{
attributes:
{
name: 'iam_id',
value: exampleUserId,
},
],
},
];
const policyRoles = [
{
role_id: 'crn:v1:bluemix:public:iam::::role:Viewer',
},
];
const accountIdResourceAttribute = {
name: 'accountId',
value: exampleAccountId,
operator: 'stringEquals',
};
const serviceNameResourceAttribute = {
name: 'serviceType',
value: 'service',
operator: 'stringEquals',
};
const policyResourceTag = {
name: 'project',
operator: 'stringEquals',
value: 'prototype',
};
const policyResources = [
{
attributes: accountIdResourceAttribute, serviceNameResourceAttribute],
tags: policyResourceTag],
},
];
const params = {
type: 'access',
* [Pricing examples](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-scenarios)
* [Default resource allocations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-default)
* [Billing](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-billing)



* [IBM Cloud and IBM Blockchain Platform charges](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-iks-ibp)
* [Storage usage](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-storage)



* [Optimizing the cost of your nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-saas-pricingibp-saas-pricing-shutdown)



[Detailed pricing scenarios](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-detailed-pricingibp-detailed-pricing)



* [Scenario comparisons](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-detailed-pricingibp-pricing-details-tabs)







 Security 

[Security](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-securityibp-security)



* [Security on the IBM Blockchain Platform console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-securityibp-security-ibp)
The credit might be listed in the Active subscriptions and credits section.

If the credit isn't on the Usage page, go to Invoices and click link with the date for your next recurring invoice. If you don't see the credit on the next recurring invoice, it is not yet added to your account. Check back later to verify that you received the credit.





 How do I get answers to my Startup with IBM questions? 

Startup with IBM Program, which was formerly the IBM Global Entrepreneur Program (GEP), is available by going to the [Startup with IBM Program](https://developer.ibm.com/startups/). The awarding and extension of credits through this IBM corporate program isn't directly supported by IBM Cloud Support. If your application to the program is approved, credits might be referred to as the Technology Incubator Program on an IBM Cloud Invoice. For more information about the program and its credits, visit the [Frequently Asked Questions for the Startup with IBM Program](https://developer.ibm.com/startups/faq).





 Where can I find my credits for IBM corporate programs? 

Credits for IBM corporate programs, such as Startup with IBM and PartnerWorld, are available within the applicable invoice in IBM Cloud. To view the credits, complete the following steps:



1. In the IBM Cloud console, go to Manage > Billing and usage, and select Invoices.
2. Select an applicable invoice.
3. Find the name of the program listed in the Current Payment Method section to see the monthly credit, applied credit, and remaining credit information.







 How do I get support? 

Go to the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter) page by clicking the Help icon ![Help icon](https://cloud.ibm.com/docs-content/v1/content/9713d864488177dc6b273b53b7f2383a81f10bc1/icons/help.svg) > Support center from the console menu bar. From there, review the list of common FAQs.
"type": "INTEGRATED",
"names": [
"TotalHits",
"TotalBandwidth",
"0XX",
"200",
"206",
"2XX",
"302",
"304",
"3XX",
"404",
"4XX",
"5XX",
"Other",
"Australasia",
"EMEA",
"India",
"Japan",
"North America",
"Rest Of APAC",
"South America"
],
"descriptions": [
"All hits to the Edge servers from the end-users.",
"Total number of megabytes transferred between the Edge to the end user.",
"Number of hits that returned response code - 0XX",
"Number of hits that returned response code - 200",
"Number of hits that returned response code - 206",
"Number of hits that returned response code - 2XX",
"Number of hits that returned response code - 302",
"Number of hits that returned response code - 304",
"Number of hits that returned response code - 3XX",
"Number of hits that returned response code - 404",
"Number of hits that returned response code - 4XX",
"Number of hits that returned response code - 5XX",
"Number of hits that returned response code not within 2XX to 5XX",
"Total number of megabytes transferred between the Edge to the end user in the region - Australasia",
"Total number of megabytes transferred between the Edge to the end user in the region - EMEA",
"Total number of megabytes transferred between the Edge to the end user in the region - India",
"Total number of megabytes transferred between the Edge to the end user in the region - Japan",
"Total number of megabytes transferred between the Edge to the end user in the region - North America",
Go to the [Payments](https://cloud.ibm.com/billing/payments) page in the IBM Cloud console.
2. Click Payment method.
3. In the Add Payment Method section, select Pay with Other, and click Submit change request. A support case to change your payment method is then created for you.



Some payment methods aren't accepted as recurring payment methods. You must manually submit the payment each month.





 India-based customers with accounts that are billed in US Dollars 

Due to current banking regulations, recurring credit card transactions might be unsuccessful for India-based customers with accounts that are billed in US Dollars. You can use one of the following methods to make a payment:



* [Make a one-time payment](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-linkedusagemakepayment)
* Request to migrate your account to be billed in India Rupees. To make a request, provide a credit card that is billed in India Rupees on the [Payment Method](https://cloud.ibm.com/billing/payments) page in the IBM Cloud console. Specify that India Rupees are in the Payment Currency section. Additional information might be requested through a Support case during the migration process.







 Making a one-time payment 

You can use a credit card to make a one-time payment at any time for any amount, whether it's for the full balance or a partial sum. The details that you enter for the one-time payment aren't recorded for future use, and aren't populated with a default amount.

To make a one-time payment, in the IBM Cloud console, go to Manage > Billing and usage, and select Payments. Click Manual Payment and complete the fields in the one-time payment section. One-time payments are reviewed and processed each day. The account balance is updated after the payment is accepted. If a late fee is assessed and you have submitted a one-time payment, contact the [IBM Cloud Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).







 Managing your payment method outside of the console
* [Storage](https://cloud.ibm.com/docs/containers?topic=containers-costspersistent_storage)
* [IBM Cloud services](https://cloud.ibm.com/docs/containers?topic=containers-costsservices)
* [Operators and other third-party integrations](https://cloud.ibm.com/docs/containers?topic=containers-costsoperators_pricing)
* [VPC worker nodes](https://cloud.ibm.com/docs/containers?topic=containers-costscharges_vpc_gen2)



* [Estimating costs](https://cloud.ibm.com/docs/containers?topic=containers-costscosts-estimate)
* [Managing costs](https://cloud.ibm.com/docs/containers?topic=containers-costscosts-manage)



[Using reservations to reduce classic worker node costs](https://cloud.ibm.com/docs/containers?topic=containers-reservationsreservations)



* [Understanding reservations](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-about)



* [Reservation usage and lifecycle](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-usage-lifecycle)
* [Billing and discounts](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-about-billing)



* [Creating a reservation](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-create)
* [Using a reservation in a cluster](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-use)
* [Reviewing reservation usage](https://cloud.ibm.com/docs/containers?topic=containers-reservationsri-review)







 Enhancing security 

[Security for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-securitysecurity)
About bandwidth metering 

To reduce your overall bandwidth costs, it's important to consider your bandwidth metering options. You can purchase and manage bandwidth metering for classic in two ways, through metering on individual devices, or through collective-metering when you add a device to a bandwidth pool.

All inbound and outbound bandwidth inside the IBM Cloud Classic infrastructure is unlimited and cost-free for your servers' use. Public egress bandwidth is charged on a tiered basis, with a set allocation for each month of your servers' use.

Bandwidth usage is measured as egress traffic on a device's public interfaces.

Bandwidth allocations are reserved for all public egress network usage. Devices with individual bandwidth metering and pool-based metering are all measured unless the device is ordered on the private network only.

Bandwidth allocation is a threshold where usage below the threshold is free or included, while usage in excess of the threshold is billed as a bandwidth overage. Bandwidth overages are billed individually per server or device, unless they participate in a bandwidth pool.

Devices added to a bandwidth pool contribute both their bandwidth allocation and bandwidth usage to form aggregated totals for the pool. If the pool usage exceeds the total pool allocation, the account owner is billed a consolidated pool overage fee.



 About device bandwidth 

You can manage each device's bandwidth allocation. When you provision certain devices, you can select the amount of bandwidth that you want to allocate to that device. For each device, you pay for a fixed amount of bandwidth allocation during a billing cycle, and receive a notification when the device is at risk of overage for the billing cycle. For more information, see [Adding Bare Metal Server bandwidth](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-adding-bare-metal-server-bandwidth) and [Adding virtual server instance bandwidth](https://cloud.ibm.com/docs/bandwidth-services?topic=bandwidth-services-adding-virtual-server-insance-bandwidth).

When the bandwidth usage on a device reaches 85% of its total allocation, the account owner receives notifications.

IBM charges for some firewall bandwidth metering.
The different lifecycle states of gateways and destinations are as follows:



 Non-functional State 

The 1.7.0 release introduced a new tiered plan pricing model. With this model came the ability to mark both Gateways and Destinations as 'Active' or 'Inactive'. Part of the new plan billing structure charges the user for the number of Gateways and Destinations that they have.



* Inactive items are not billed
* Inactive Destinations do not have a provisioned cloud port.
* All Destinations within an inactive gateway will also be inactive and cannot be reactivated until their Gateway is also set Active.
* Inactive items are considered Non Functional. Inactive items cannot be in any of the Functional states.



When you [downgrade the plan](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-secure-gateway-service-planschanging-plans), it will update all gateways to be inactive, all provisioned cloud port of the destinations will be reset. If you want to reactivate your gateway, you can click the wrench button in the gateway panel to configure the Non-functional State. For details, see [Reactivate gateway](https://cloud.ibm.com/docs/SecureGateway?topic=SecureGateway-add-sg-gwreactivate).





 Functional States 

When a gateway or destination is marked active it will be billed. Active states for Gateways and Destinations are below:



* Enabled - the gateway or destination is ready for use under normal circumstances.
* Disabled - the gateway or destination has been disabled.



* Gateways - clients will be unable to flow data to the disabled gateway.
* Destinations - clients will be unable to create connections to these disabled destinations.











 How do I know the data activities on the Secure Gateway Client? 

On SecureGateway Client, change the log level to TRACE to know the data activities on the client. The following information will be displayed after requests are sent.

Data size sent from request application:

[TRACE] Connection <connection ID> transmitted data: <size> bytes

Data size sent from destination:

[TRACE] Connection <connection ID> received data: <size> bytes
* [Operators and other third-party integrations](https://cloud.ibm.com/docs/openshift?topic=openshift-costsoperators_pricing)
* [VPC worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-costscharges_vpc_gen2)



* [Estimating costs](https://cloud.ibm.com/docs/openshift?topic=openshift-costscosts-estimate)
* [Managing costs](https://cloud.ibm.com/docs/openshift?topic=openshift-costscosts-manage)



[Using reservations to reduce classic worker node costs](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsreservations)



* [Understanding reservations](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-about)



* [Reservation usage and lifecycle](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-usage-lifecycle)
* [Billing and discounts](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-about-billing)



* [Creating a reservation](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-create)
* [Using a reservation in a cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-use)
* [Reviewing reservation usage](https://cloud.ibm.com/docs/openshift?topic=openshift-reservationsri-review)







 Enhancing security 

[Security for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-securitysecurity)
Possible values include High, Medium, and Low. 
 text The payment term, listed as a string. 
 normalized_text The normalized text, if applicable. 
 interpretation The details of the normalized text, if applicable. 
 value A string listing the value that was found in the normalized text. 
 numeric_value An integer or float expressing the numeric value of the value key. 
 unit A string listing the unit of the value that was found in the normalized text. 
 location The location of the payment term as defined by its begin and end indexes. 
 provenance_ids An array of hashed values that you can send to IBM to provide feedback or receive support. 







 Contract currencies 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The contract_currencies array identifies the contract currency or currencies as declared in the document.



 contract_currencies Description 

 confidence_level The confidence level of the identification of the contract currency. Possible values include High, Medium, and Low. 
 text The contract currency, listed as a string. 
 text_normalized The normalized text of the text if applicable, listed as a string in [ISO-4217](https://www.iso.org/iso-4217-currency-codes.html) format. 
 location The location of the contract currency as defined by its begin and end indexes. 
 provenance_ids An array of hashed values that you can send to IBM to provide feedback or receive support. 







 Provenance 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

Each object in the types and categories arrays includes a provenance_ids array. The provenance_ids array has one or more keys. Each key is a hashed value that you can send to IBM to provide feedback or receive support.
(https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/sell/images/Usage_metering_role.svg)

Figure 1. Understanding the function of the IBM Cloud Usage Metering service for automating the submission of usage data.



* You must submit usage records for the current month by the second day of the following month.
* IBM Cloud is configured for a monthly billing cycle and time is represented in Coordinated Universal Time (UTC).
* You must test usage submission and validate your results to describe how the monthly billing cycle is calculated.



For more information about pricing, see [How to calculate your costs](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-costcost).



 Configuration properties 

The following properties define how IBM Cloud meters and rates usage submissions for product plans:

Unit
: Metrics to be metered, for example, ApiCall, Bytes, Hours, Instances, and Nodes.

Aggregation
: How the metered unit data is compiled, for example INSTANCES_BY_MONTH, or ACTIVE_HOURS_BY_MONTH.

Metering model
: How the usage submission data is processed, as shown in the metering and model types table.

Resource name
: The name of the resource that is being measured, for example, storage, instance, virtual server, or bytes transmitted.

Unit name
: The descriptive name of the unit if the default name isn't relevant for the product.





 Metering model types 

See the following table for information about the available metering models and a brief description of each type:



Table 1. Metering model

 Type Description 

 standard_add Add quantity from all submitted usage records for a month. 
 standard_max Maximum quantity from all submitted usage records for a month. 
 standard_avg Average quantity from all submitted usage records for a month. 
 dailyproration_max Calculated daily maximum. The sum up all the days for the month. 
 dailyproration_avg Calculated daily average. The sum up all the days for the month.
As with all accounts, resources are tied to the resource group and account in which they're created, so they can't be moved between accounts in the enterprise. However, the enterprise's flexible account structure means you can move resources within the enterprise by moving the accounts that contain them.





 Top-down usage reporting 

From the enterprise account, you can view resource usage from all accounts in the enterprise. Starting at the enterprise level, you see estimated usage costs that are broken down by account and account groups. You can navigate down within the enterprise structure to see the costs within each level. At the account level, enterprise users can view costs for each type of resource or service in the account.

Because access in the enterprise is separate from access in each account, enterprise users can't automatically create or manage resources within the child accounts. Similarly, users in each account can continue to view their past and current usage from the Usage page regardless of whether they have enterprise access.

For more information, see [Viewing usage in an enterprise](https://cloud.ibm.com/docs/billing-usage?topic=billing-usage-enterprise-usage).





 Isolated user and access management 

Enterprises keep user and access management isolated between the enterprise and its child accounts to provide greater security for your accounts' data. The users and their assigned access in the enterprise account are entirely separate from those in the child accounts, and no access is automatically inherited between the two types of accounts.

The user lists for each account are only visible to the users who are invited to that account. Just because a user is invited and given access to manage the entire enterprise, it doesn't mean that they can view the users who are invited to each child account. User management in each enterprise and each account is entirely separate and must be managed by the account owner or a user given the Administrator role on the User management account management service in the specific account.

Similar to how user management is entirely separate in each account and the enterprise itself, so is access management. This separation means that users who manage your enterprise can't access account resources within the child accounts unless you specifically enable them to.
* Multiple values in arrays of row_header_ids and row_header_texts elements indicate a possible hierarchy of row headers.
* Multiple values in arrays of column_header_ids and column_header_texts elements indicate a possible hierarchy of column headers.







 **Note on unit values 

The value of unit is the [ISO-4217 currency code](https://www.iso.org/iso-4217-currency-codes.html) identified for the currency amount (for example, USD or EUR). If the service cannot disambiguate a currency symbol (for example, $ or £), the value of unit contains the ambiguous symbol as-is.





 Note on location objects 

The Element Classification enrichment is deprecated and will no longer be available, effective 10 July 2020.

The location object is included with the majority of element definitions. The object identifies the location of an element. The object contains two index numbers, begin and end. The index numbers indicate the beginning and ending positions, respectively, of the element as character numbers in the HTML document that the service created from your input document.

For example, a text string with the value Amount due might have a corresponding location object such as

{
...
"location": {
"begin": 2510,
"end": 2519
}
...
}

The begin index indicates that the string begins at character position 2510 in the transformed HTML; this is the location of the letter A in Amount. The end index indicates that the string ends at character position 2519; this is the location of the letter e in due.