vania-janet/multiturn-rag-retrieval-data huggingface dataset:
<br>For example, if filter A references filter B in its before field, A is applied before B. 
 ge <br>Optional <br>Integer The IP prefix GE. The GE (greater than or equal to) value sets the minimum prefix length on which the filter action is applied. 
 le <br>Optional <br>Integer The IP prefix LE. The LE (less than or equal to) value sets the maximum prefix length on which the filter action is applied. 





 Example 

This example shows how to add a prefix filter:

resource "ibm_tg_connection_prefix_filter" "test_tg_prefix_filter" {
gateway = ibm_tg_gateway.new_tg_gw.id
connection_id = ibm_tg_connection.test_ibm_tg_connection.connection_id
action = "permit"
prefix = "192.168.100.0/24"
le = 32
ge = 24
}

To remove a prefix filter, use the terraform destroy -target=ibm_tg_connection_prefix_filter.[prefix filter name] command.
Set filters at a private catalog level for fine-grained control of which products in the public catalog are available only to the users you choose. The following example applies the filter id_filters where AdvancedMobileAccess-d6aece47-d840-45b0-8ab9-ad15354deeea is a product ID.

curl -X 'PUT' 'https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogs/<catalog-id>'
-H 'accept: application/json' -H 'Content-Type: application/json' -H "Authorization: ${IC_IAM_TOKEN}" -d '{"label": "testcurlcatalog4", "short_description": "testing creating a catalog through curl", "catalog_filters": { "include_all": false, "id_filters": { "include": { "filter_terms": [ "AdvancedMobileAccess-d6aece47-d840-45b0-8ab9-ad15354deeea" ] } } }}'

See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curlreplace-catalog) for more information.





 Catalog filters 

The following table lists the filters that you can use to customize which products in the public catalog are available to users in your account.

Category

Compliance

Delivery method



Table 1. Options for filtering by category
Use the buttons before the table to change the context of the table. The column headers identify the options for fitering based on filter type.

 Option Description 

 AI / Machine Learning Products that enable systems to learn from data rather than through explicit programming. 
 Analytics Products that facilitate the analysis of data, typically large sets of business data, by the use of mathematics, statistics, and other means. 
 Blockchain Products that facilitate the process of recording transactions and tracking assets in a business network. 
 Compute Infrastructure resources that serve as the basis for building apps in the cloud.
Depending on the route filter that you want to configure, click Import route filters or Export route filters.
4. For Default, specify to permit or deny all routes not specified by a route filter.
5. To create filters to add to the list, or to prioritize filters, click Configure filters.
6. Save your configuration. You are returned to the Details page where your route configuration is displayed.







 Configuring route filters from the CLI 

You can create route filters with the CLI using the [exportroutefilter-create](https://cloud.ibm.com/docs/dl?topic=dl-dl-cli&interface=cliexport-route-filter-create) and [importroutefilter-create](https://cloud.ibm.com/docs/dl?topic=dl-dl-cli&interface=cliimport-route-filter-create) commands. For example, the following command shows how to create an export route filter:

ibmcloud dl export-route-filter-create 58e4f46f-0dab-0000-9432-3df974db0618 --action deny --prefix 10.10.10.0/24 --ge 30 --le 26

Where:

58e4f46f-0dab-0000-9432-3df974db0618
: Specifies the ID of the gateway.

--action deny
: Specifies the export route filter action. Valid values are 'permit' or 'deny'.

--prefix 10.10.10.0/24
: Specifies an IPv4 subnet CIDR indicating both the address and mask length.

--le LE
: Specify a maximum matching length (LE, less than or equal to). Optional. For more information, see [Route filtering rules](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes&interface=uiroute-filtering-rules).

--ge GE
: Specify a minimum matching length (GE, greater than or equal to).
Must be in NAME=VALUE format. This action adds a new CloudEvents extension or overrides an existing CloudEvent attribute. Specify one extension per --extension option; for example, --ext extA=A --ext extB=B. This value is optional.

--extension-rm, --ext-rm
: Remove CloudEvents extensions to send to the destination by specifying the name of the key. Specify one extension per --ext-rm option; for example, --ext-rm extA --ext-rm extB. This value is optional.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--password, -p
: The password that is used to authenticate to the Kafka instance. If you specify the --password option, you must not specify the --secret option. This value is optional.

--path
: The path within the destination application where events are forwarded; for example, /events. The default path is the root URL of the destination application. This option can only be specified if destination-type is app. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--secret, -s
: The name of the secret that is used to authenticate to the Kafka instance and which includes both username and password keys. If you specify the --secret option, you must not specify the --username or --password options. This value is optional.

--topic, -t
: Set a topic in the Kafka source. Topics are used to filter messages to consume. This option can be specified multiple times. This value is optional.

--username, -u
Must be in NAME=VALUE format. This action adds a new CloudEvents extension or overrides an existing CloudEvent attribute. Specify one extension per --extension option; for example, --ext extA=A --ext extB=B. This value is optional.

--extension-rm, --ext-rm
: Remove CloudEvents extensions to send to the destination by specifying the name of the key. Specify one extension per --ext-rm option; for example, --ext-rm extA --ext-rm extB. This value is optional.

--output, -o
: Specifies the format of the command output. Valid options are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--password, -p
: The password that is used to authenticate to the Kafka instance. If you specify the --password option, you must not specify the --secret option. This value is optional.

--path
: The path within the destination application where events are forwarded; for example, /events. The default path is the root URL of the destination application. This option can only be specified if destination-type is app. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--secret, -s
: The name of the secret that is used to authenticate to the Kafka instance and which includes both username and password keys. If you specify the --secret option, you must not specify the --username or --password options. This value is optional.

--topic, -t
: Set a topic in the Kafka source. Topics are used to filter messages to consume. This option can be specified multiple times. This value is optional.

--username, -u
Make sure to exclude all public catalog products by setting the include_all field has a boolean value of false for each catalog_filters object. To specify the products you want to include you can filter by category_filters or id_filters. Give filter_terms the product property or product ID you want to include. In this example, AdvancedMobileAccess-d6aece47-d840-45b0-8ab9-ad15354deeea is a product ID.

See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=nodereplace-catalog) for more command options.





 Setting the visibility of the IBM Cloud catalog by using the API 

To hide the public catalog in an account, make sure the hide_IBM_cloud_catalog field has a boolean value of true. Alternatively, you can give the include_all field a boolean value of false for each account_filters object. Then only the private catalogs you create should be displayed in your account.

curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount"
-H "accept: /"
-H "Authorization: {iam-bearer-token}"
-d '{"id":"string","hide_IBM_cloud_catalog":true,"account_filters":{"include_all":true,"category_filters":{"additionalProp1":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp2":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp3":{"include":true,"filter":{"filter_terms":["string"]}}},"id_filters":{"include":{"filter_terms":["string"]},"exclude":{"filter_terms":["string"]}}}}'
* Prioritize direct links with AS prepends - Adjust route preference by lengthening AS paths with multiples of the BGP Autonomous System Number (ASN). When the prefix is matched, the longer AS path becomes a lower priority for the BGP router. For more information, see [Prepending an AS path to influence route priority](https://cloud.ibm.com/docs/dl?topic=dl-prepend-as-paths).
* Filter your import routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all import routes are permitted. Next, click Configure filters to start creating import route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see [Filtering routes](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes).
* Filter your export routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all export routes are permitted. Next, click Configure filters to start creating export route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration. For more information, see [Filtering routes](https://cloud.ibm.com/docs/dl?topic=dl-filter-routes).



10. In the Connections section, select the type of network connection that you want to bind to the Direct Link gateway. You can select a connection type when you create a direct link, or after your direct link is provisioned.

Select from the following connection types:



* Select Direct resources (default) to create a direct, private connection between your on-premises network and IBM Cloud deployment. Optionally, choose a connection and enter a connection name. To add multiple network connections to the Direct Link gateway, click Add connection +. You can create one of the following connections:



* Classic infrastructure networks allow you to connect to IBM Cloud classic resources. Only one classic infrastructure connection is allowed per Direct Link gateway.
The following table outlines the parameters that you can define to set the filtering rules in a cluster:



Table 1. Parameters to define conditions on containers

 Parameter Condition 

 container.image Container image name 
 container.name Container name 
 container.label.* Container label 
 kubernetes.object.* Kubernetes object. An object can be a pod, a namespace, etc. 
 kubernetes.object.annotation.* Kubernetes object annotation 
 kubernetes.object.label.* Kubernetes object label 
 all Default rule to specify all objects 



Consider the following information on how the monitoring agent applies the rules that you define in the container_filter section:



* You define conditions by configuring them with the include and exclude filtering parameters.
* The first matching rule in the list determines if the container is included or excluded.
* The conditions consist of a key name and a value. If the given key for a container matches the value, the rule is applied.
* When a rule contains multiple conditions, all the conditions need to match for the rule to be applied.



Complete the following steps to filter out containers that a monitoring agent monitors in a cluster:



1. Set up the cluster environment. Run the following commands:

First, get the command to set the environment variable and download the Kubernetes configuration files.

ibmcloud ks cluster config --cluster <cluster_name_or_ID>
2. Edit the sysdig-agent-configmap.yaml file.

Run the following command:

kubectl edit configmap sysdig-agent -n ibm-observe
3. Make changes. Add the use_container_filter entry and container_filter section or update the the existing entries.

For example, see the following extract of a config map:

 Enable the feature
use_container_filter: true

 Include or exclude conditions
container_filter:
- include:
container.image: appdomain/my-app-image
- include:
container.name: my-java-app
- exclude:
See the [Catalog Management API](https://cloud.ibm.com/apidocs/resource-catalog/private-catalog?code=curlupdate-catalog-account) for more information.





 Managing access to products for all users by using the API 

You can use filters to manage which products in the public catalog are available to all users in your account. For example, you might want to restrict access to third-party products. Or, you might want users to work with a specific software type.

If your account is a parent account in an IBM Cloud enterprise, the filters that you set apply to all child account groups and accounts. For more information, see [Managing products for IBM Cloud enterprise](https://cloud.ibm.com/docs/account?topic=account-catalog-enterprise-restrict).

curl -X "PUT" "https://cm.globalcatalog.cloud.ibm.com/api/v1-beta/catalogaccount"
-H "accept: /"
-H "Authorization: {iam-bearer-token}"
-d '{"id":"string","hide_IBM_cloud_catalog":true,"account_filters":{"include_all":true,"category_filters":{"additionalProp1":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp2":{"include":true,"filter":{"filter_terms":["string"]}},"additionalProp3":{"include":true,"filter":{"filter_terms":["string"]}}},"id_filters":{"include":{"filter_terms":["string"]},"exclude":{"filter_terms":["string"]}}}}'

The options for {accountFilters} are: include_all, category_filters, and id_filters.
* Search logs
* Filter logs



Therefore, you need the following policies:



* An IAM policy for the IBM Log Analysis service with the platform role Viewer. This policy grants permissions to view the service instance details through the command line and in the IBM Cloud dashboard.
* An IAM policy for the IBM Log Analysis service with the service role Reader. This policy grants permissions to view, filter and search logs through the logging web UI.



Note: As an administrator of the service, when you grant a user these policies, consider doing it within the context of a resource group. An IBM Log Analysis instance is provisioned within the context of a resource group. Therefore, grant access permissions to users within the context of the resource group.

Complete the following steps to assign a user both policies for the IBM Log Analysis service within the context of a resource group:



1. From the menu bar, click Manage > Access (IAM), and then select Users.
2. From the row for the user that you want to assign access, select the Actions menu, and then click Assign access.
3. Select Assign access within a resource group.
4. Select a resource group.
5. If the user does not have a role already granted for the selected resource group, choose a role for the Assign access to a resource group field.

Depending on the role that you select, the user can view the resource group on their dashboard, edit the resource group name, or manage user access to the group.

You can select No access, if you want the user to only have access to the IBM Log Analysis service in the resource group.
6. Select IBM Log Analysis.
7. Select the platform role Viewer.
8. Select the service role Reader.
9. Click Assign.
FilterID b4dbe0a6-c52d-4128-cc32-6f53d86bc82b
Prefix 10.0.250.0/24
Action permit
Ge 28
Le 32
Before
Created 2022-02-28T12:35:09.226-06:00
Updated 2022-02-28T12:35:09.226-06:00





 Deleting prefix filters from the CLI 

To delete prefix filters from the CLI, follow these steps:

ibmcloud tg prefix-filter-delete GATEWAY_ID CONNECTION_ID FILTER_ID [-f, --force]

Where:



* GATEWAY_ID: ID of the gateway that the prefix filter will be deleted from.
* CONNECTION_ID: ID of the connection that the prefix filter will be deleted from.
* FILTER_ID: ID of the prefix filter that is being deleted.
* --force, -f: Force the deletion operation without confirmation.







 Example: Deleting a prefix filter 

This is an example of deleting a prefix filter from the CLI.

ibmcloud tg pfd 9f559c43-63f4-4da5-b312-b525a8dce185 6c1bdc19-4adb-4760-8cdc-ef3b74b626f7 b4dbe0a6-c52d-4128-cc32-6f53d86bc82b

This deletes filter b4dbe0a6-c52d-4128-cc32-6f53d86bc82b on gateway 9f559c43-63f4-4da5-b312-b525a8dce185 connection 6c1bdc19-4adb-4760-8cdc-ef3b74b626f7 and cannot be undone. Continue [y/N] ?> Y
For more information, see [Building a custom extension](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-build-custom-extension) and [Adding an extension to your assistant](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-add-custom-extension).





 8 June 2023 

Edit step titles
: You can now add and edit titles for each step, which can help you more easily identify what a step does in an action. For more information, see [Editing actions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-build-actions-overview).

New message when deleting a subaction
: If you delete an action that is a subaction, there is a new message that lists all the actions that call the subaction and asks you to confirm the deletion. The message helps you preserve dependencies between actions and subactions.





 5 June 2023 

Filtering the list of actions
: You can locate specific actions by filtering the list by subactions, by custom extension, or by variable. For more information, see [Filtering actions](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-filter-actions).





 29 May 2023 

New expression choice for setting a session variable
: Previously, to use an expression to set or modify a variable value, you needed to pick an existing variable or create a new one and select the expression option. Now you can use a new Expression choice to write an expression directly without first picking a variable. For more information, see [Storing a value in a session variable](https://cloud.ibm.com/docs/watson-assistant?topic=watson-assistant-manage-infostore-session-variable).

Changes to validation of OpenAPI specifications
: When you build a custom extension, you work with OpenAPI specification files. This release includes changes to the validation of OpenAPI files, which might affect the connection between your actions and extensions
: Metrics are now available in the Frankfurt region.







 November 2021 



 01 November 2021 

The following changes were made in build 8243:

Audit messages
: Order customer supplied fields last in audit messages.

Changes feed
: Reduce changes feed rewinds when nodes are down or shards are moved.

View collation
: Fix reduce view collation results for Unicode equivalent keys.







 October 2021 



 01 October 2021 

The following changes were made in build 8238:

Changes feed
: Use shards moved from other nodes to help prevent changes feed rewind.

Error message
: Reduce frequency of No DB shards could be opened error message.

Shards with purge sequences
: Fix splitting shards with large purge sequences.

View results
: Fix view results with limit=0 and sorted=false.

Sort view results
: Properly sort view results with descending=true when a key list is provided.

Row aggregation
: Stabilize view merge row aggregation.







 September 2021 



 1 September 2021 

The following changes were made in build 8220.

Changes feed rewinds
: Avoid changes feed rewinds after shard moves.

Response code
: Fix response code for attachment deletion with wrong revision.

Indexes
: Ensure that indexes are correctly closed.







 August 2021 



 1 August 2021 

The following changes were made in build 8202:

IAM trusted profiles
: Support IAM trusted profiles.





 15 August 2021 

The following changes were made in build 8201:

Improvements
: Internal bug fixes.







 June 2021 



 1 June 2021 

The following changes were made in build 8194:

API task filtering
: Bug fixes, including account API key task filtering.

Replication support
: Support replication [basic auth credentials in auth object](https://github.com/apache/couchdb/pull/3586).

Basic auth credentials
: No longer display basic auth credentials (for example, username:) in the output of these endpoints:



* _scheduler/jobs
* _scheduler/docs
* _active_tasks









 April 2021 



 1 April 2021
Save your certificate authority certificate to a file named ca-cert. It must be that exact name.
5. Create a secret in the kube-system namespace for the ca-cert file. When you create your logging configuration, use the secret name for the --ca-cert option.

kubectl -n kube-system create secret generic --from-file=ca-cert
6. Create a log forwarding configuration. For more information about the parameters, see the [Understanding logging configuration options table](https://cloud.ibm.com/docs/containers?topic=containers-healthenable-forwarding).

ibmcloud ks logging config create --cluster <cluster name or id> --logsource <log source> --type syslog --syslog-protocol tls --hostname <ip address of syslog server> --port <port for syslog server, 514 is default> --ca-cert <secret name> --verify-mode <defaults to verify-none>







 Filtering logs that are forwarded 

You can choose which logs to forward to your external server by filtering out specific logs for a period of time. You can differentiate between the different filtering options by using options.



Table 2. Understanding the options for log filtering

 Parameter Description 

 <cluster_name_or_ID> Required: The name or ID of the cluster that you want to filter logs for. 
 <log_type> The type of logs that you want to apply the filter to. Currently all, container, and host are supported. 
 <configs> Optional: A comma-separated list of your logging configuration IDs. If not provided, the filter is applied to all the cluster logging configurations that are passed to the filter. You can view log configurations that match the filter by using the --show-matching-configs option. 
 <kubernetes_namespace> Optional: The Kubernetes namespace that you want to forward logs from. This option applies only when you are using log type container. 
 <container_name> Optional: The name of the container from which you want to filter logs.