vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can delete the existing collector and create a new one with the Object Storage bucket location that you want to use.





 Are virtual appliances (IKS workers, ROKS, LBaaS, VPN gateway) included in the flow log collector data output? 

Flow Logs for VPC supports:



* IBM Cloud Kubernetes Service (IKS) workers
* RedHat OpenShift Kubernetes Service (ROKS)
* Load Balancer as a Service (LBaaS)



VPN gateway is also available at a VPC and subnet level.

At this time, flow log collection does not include support for bare metal server network interfaces and endpoint gateways.





 Is there a viewer or filter for flow logs? 

Flow Logs for VPC does not have a native viewer or filter. However, SQL Query is a viable option.





 Can I modify the target scope for a flow log collector? 

You cannot change the target scope for an existing flow log collector. You can delete the existing collector and create a new one with the target scope that you want to use.





 Do I need to suspend a flow log collector before I delete it? 

No, you can delete a flow log collector at any time, whether it is active or not.
For more information, see [Adjusting file share IOPS](https://cloud.ibm.com/docs/vpc?topic=vpc-adjusting-share-iops&interface=ui).
* Can I change a file share profile?

 Can I change a file share profile? 

Yes, you can use the UI, CLI, or API to update a file share profile. You can change among IOPS tier profiles. When you select a custom profile or dp2 high-performance profile, you specify the maximum IOPS based on the file share size.

You cannot use the UI, CLI, or API to update multiple file shares in a single operation. For more on this issue, see [troubleshooting File Storage for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-troubleshooting-file-storage).
* How secure is my data?

 How secure is my data? 

All data is encrypted at rest by default with IBM-managed encryption. You can also encrypt your file shares with your own root key, which gives your more control over your data security. For example, you can rotate, suspend, delete, and restore your root keys. For more information, see [Creating file shares with customer-managed encryption](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-encryption).

You can also enable secure end-to-end encryption of your file share data by setting up data encryption in transit. Encryption in transit for your file shares lets you establish an encrypted mount connection between the virtual server instance and storage system using the Internet Security Protocol (IPsec) security profile. For more information, see [Enabling file share encryption in transit secure connections](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-eit).
* Is there support for security groups and network ACLs?

 Is there support for security groups and network ACLs? 

Yes. You can specify a security group access control mode to restrict mounting file shares to specific instances in your VPC.
For more information, see [Compact download for Schematics Workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-compact-download).
* How do I delete a workspace when the delete fails

If a resource has already been deleted outside of Schematics, a workspace delete operation will as the resource no longer exists.

You need to delete the workspace and NOT destroying the resources as if resource is not available. For more information, see [Deleting a workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks).
* What is the best way to deploy a Helm chart using credentials or secrets?

The best way is to use IBM Cloud catalog to manage the Helm charts where inside the catalog you can keep the credentials and mark it as secured. For more information, see [List of catalog that is related to Helm](https://cloud.ibm.com/catalog?search=label%3Ahelm).
* How do I address job failures caused by maintenance activities?

The unexpected impact due to maintenance results in the failure of the running activities in Schematics Workspace. Such workspace and the ongoing activity are marked as Failed. The user can then re-execute the activity. For more information, see [workspace state diagram](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-state&interface=uiworkspace-state-diagram).
* How do you set the Git release tag?

2021/11/08 12:34:06 ----- New Action -----
2021/11/08 12:34:06 Request: RepoURL=https://github.ibm.com/wh-hp-insights/hi-cloud-automation, workspaceSource=Schematics, Branch=2021.10, Release=, Folder=terraform-v2/workspace-hi-qa-automation-app
Setting dual authorization policies for keys 

You can use IBM Cloud® Hyper Protect Crypto Services to set dual authorization policies for individual root keys or standard keys.

Dual authorization is an extra policy that helps to prevent accidental or malicious deletion of encryption keys in your Hyper Protect Crypto Services instance. When you enable this policy at the key level, Hyper Protect Crypto Services requires an authorization from two users to delete an encryption key.

After you enable dual authorization at the key level, the policy that is associated with the key can no longer be changed to allow a single authorization to delete the encryption key.

To enable dual authorization settings at the instance level, check out [Managing service settings](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-dual-auth).



 Managing dual authorization policies with the key management service API 

Consider the following items before you enable dual authorization for a key:



* Determine whether a dual authorization policy is required for the key. As a security admin, assess the sensitivity of your workload to determine whether a key requires a dual authorization policy based on your requirements. After you enable dual authorization for a key, the policy can no longer be changed to allow a single authorization to delete the key.
* Determine who can authorize deletion of your Hyper Protect Crypto Services resources. After you create a dual authorization policy for a key, the key will require [an action from two users](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-dual-auth-keys) before it can be deleted. Be sure to identify two distinct users with the [appropriate levels of access](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-manage-accessservice-access-roles) to the instance or key.



To learn how to delete a key that has a dual authorization policy, see [Deleting keys using dual authorization](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-delete-dual-auth-keys).



 Viewing a dual authorization policy for a key
(https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqschematics-vs-cloud-resource-faq)
* [Are changes to Git repos refreshed in Schematics?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqedit-resource-confg-faq)
* [Where is the Terraform state file stored?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqresource-state-faq)
* [Are resources removed on delete workspace?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqdelete-resource-wks-faq)
* [Can I set environment variables for workspaces?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqworkspace-env-vars)
* [Does drift detection run automatically?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqdrift-automatic-faq)
* [How can I initiate drift detection?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqdrift-initiate-faq)
* [Where can I see the status of a drift detection job ?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqdrift-status-faq)
* [Can I interrupt or terminate running jobs?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqstopping-job-faq)
* [How do I correct an Incorrect Location Input error?]
After you [install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-devtools-manually), you can delete a toolchain from the command line by using the [ibmcloud dev toolchain-delete](https://cloud.ibm.com/docs/cli?topic=cli-idt-clitoolchain-delete) command.





 Why can't I view my toolchains in my DevOps dashboard? 

 What’s happening 

When you go to the DevOps dashboard, your toolchains aren't displayed.

 Why it’s happening 

Your toolchain doesn't show in the toolchain unless you have the proper location selected. DevOps Insights is only available in three locations: Dallas, Frankfurt, and London.

 How to fix it 

On your toolchain page, change the location to Dallas, Frankfurt, or London to show all of your DevOps Insights integrated toolchains.





 Why can't I create a toolchain when the root key is disabled? 

 What’s happening 

When you attempt to create a toolchain, the following notification is displayed: The root key of the Key Management Service instance that was configured for the Continuous Delivery service in the selected resource group and region is disabled.

 Why it’s happening 

When you create a toolchain, you must protect it by using a root key for encryption that is enabled.

 How to fix it 

Use one of the following methods to enable the root key for encryption:



* [Enable the root key for the IBM® Key Protect for IBM Cloud® instance](https://cloud.ibm.com/docs/key-protect?topic=key-protect-disable-keysenable-root-key) that is associated with your Continuous Delivery service, in the region where you want to create a toolchain.
For example, if object storage origin s3-example.object-storage.com with bucket name xyz-bucket-name is added in path /example-cos/, when a user opens the CDN URL cdn.example.com/example-cos/, the CDN edge server retrieves the content from s3-example.object-storage.com/xyz-bucket-name/.







 What's the difference between the origin on the Settings page and the origins on the Origins page? 

The Settings page shows the origin path created during CDN provisioning. You cannot edit or delete it. However, on the Origins page, you can configure different types of origins (COS or origin server). You can also edit or delete origins on this page.





 Why can't I change the protocol and port for an origin? 

The displayed protocol and port options match what you selected when you ordered the CDN. For example, if you selected an HTTP port when you ordered a CDN, only the HTTP port option is shown as part of Add Origin.





 How many origins can I add to a CDN? 

See [Known limitations](https://cloud.ibm.com/docs/CDN?topic=CDN-limits-and-maximum-valuesis-there-a-limit-on-the-number-of-origin-and-ttl-entries) for the number of origins per CDN.
Why can't I assign keys to Azure Key Vault? 

After I create an Azure Key Vault key using Hyper Protect Crypto Services with Unified Key Orchestrator, I can't assign the key to an external keystore of type Azure Key Vault.

  What’s happening 

After you create a key in Hyper Protect Crypto Services with Unified Key Orchestrator and assign it to a keystore of Azure Key Vault, you cannot find the key that is listed in the connected Key Vault instance in the Azure cloud or use it for encryption.

  Why it’s happening 

You might have accidentally deleted a key named EKMF-BYOK-KEK-FOR-IMPORT in the Azure Key Vault instance that you connect to. You can assign keys to your Azure Key Vault only if a key named EKMF-BYOK-KEK-FOR-IMPORT exists in the Azure Key Vault instance. By default, this key is automatically created when you successfully connect to your Azure Key Vault instance.

  How to fix it 

Create a key from the Azure Key Vault UI based on the following key settings. And then, reassign target keystores for keys that you create from the Hyper Protect Crypto Services UI again. For detailed instructions, see [Editing key details with the IBM Cloud console](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-edit-kms-keys).



 Parameter  Value                                                         

 Options    Generate Key Encryption Key for Importing HSM-protected Keys  
 Name       EKMF-BYOK-KEK-FOR-IMPORT                                      
 Key type   RSA-HSM                                                       
 Enabled    Yes
I have existing VPCs. Can I create a file share within that VPC? 

Yes.
* What interfaces are supported for this release to create file shares?

 What interfaces are supported for this release to create file shares? 

You can use the UI, CLI, API or Terraform to create and manage your file shares.
* Can I mount file shares on a Windows operating system?

 Can I mount file shares on a Windows operating system? 

No, file shares can be mounted only on supported on Linux operating systems or a z/OS-based IBM Cloud® Compute Instance that support NFS file shares. For more information, see the mounting information for [Red Hat](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-RHE), [CentOS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-mount-centos), and [Ubuntu](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-ubuntu) Linux distributions, or [z/OS](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-vpc-mount-zos) systems.
* What is the minimum NFS version supported?

 What is the minimum NFS version supported? 

File Storage for VPC requires NFS versions v4.1 or higher.
* What features are supported in this release?

 What features are supported in this release? 

In this release, you can:



* Create a file share.
* Mount a file share to one or multiple virtual server instances across multiple VPCs within the same zone or across zones.
* Restrict access to a specific virtual server instance when mounting a file share by using security groups.
* Enable end-to-end encryption in transit for file share data.
* Delete a file share.
* Delete all mount targets or delete a single mount target.
[IBM Cloud Object Storage package](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_install) Installable You can use the installable cloud-object-storage package to [read, write, and delete](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_obstorage_install) from an IBM Cloud Object Storage bucket. 







 Setting up the IBM Cloud Object Storage trigger 

With the IBM Cloud Object Storage trigger, you can listen for changes to GPS street data stored in an IBM Cloud Object Storage bucket. Then, when changes occur, you can trigger the automatic regeneration of a GPS map so that users can have access to the latest street data for their GPS application.

What is the IBM Cloud Object Storage trigger?
: The IBM Cloud Object Storage package is a pre-installed Cloud Functions package that you can use to create triggers to listen for changes to objects in a bucket. When a bucket change occurs, the trigger is fired. You can then create actions and rules to process object changes from the bucket. The trigger is available in the us-east, us-south, eu-gb, eu-de, and jp-tok regions.

How does the trigger work?
: Once configured, the trigger listens for changes to a bucket and fires on successful change events. When you create the trigger, you can specify a parameter that filters trigger activations based on the bucket change event type, such as write events,delete events, or all events. You can also filter the trigger activations by object prefix, suffix, or both.

The trigger is fired for each successful bucket change event. Each object change in a batch request is handled individually. For example: A batch request to delete 200 hundred objects would result in 200 individual delete events and 200 trigger fires. For more information, see [Details and limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-pkg_obstoragepkg_cos_limits).

How do I use the trigger?
I tried to delete a toolchain from the command line by using the ibmcloud resource service-instance-delete command, and the command fails with the following error message:

Error Code: RC-ServiceBrokerErrorResponse Message: description : Toolchain delete must be performed from the toolchain dashboard

 Why it’s happening 

Toolchains are a special type of resource on the Cloud platform that you currently can't delete by using the ibmcloud resource CLI.

 How to fix it 

To delete a toolchain:



1. From the IBM Cloud console, click the menu icon ![hamburger icon](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/icon_hamburger.svg), and select DevOps. On the Toolchains page, click the toolchain to delete. Alternatively, on the app's Overview page, on the Continuous delivery card, click View toolchain.
2. Click the Actions menu, then select Delete. Deleting a toolchain removes all of its tool integrations, which might delete resources that are managed by those integrations.
3. Confirm the deletion by typing the name of the toolchain and clicking Delete.



You can use the IBM Cloud CLI Developer Tools (ibmcloud dev) commands to delete toolchains. After you [install the IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-devtools-manually), you can delete a toolchain from the command line by using the [ibmcloud dev toolchain-delete](https://cloud.ibm.com/docs/cli?topic=cli-idt-clitoolchain-delete) command.





 Why can't I view my toolchains in my DevOps dashboard? 

 What’s happening 

When you go to the DevOps dashboard, your toolchains aren't displayed.
Why can't I assign my resource to a new resource group? 

You can't reassign an IBM Cloud® resource to a different resource group after it has already been created.

  What’s happening 

You don't have the option to move a resource from one resource group to another.

  Why it’s happening 

Resources can't be moved after they are assigned to a resource group.

  How to fix it 

To correct this issue, you can try to delete the resource and create a new instance of it from the catalog. This way, you can be sure to assign the new instance to the correct resource group.
kubectl delete crd subscriptions.operators.coreos.com
kubectl delete crd catalogsources.operators.coreos.com
kubectl delete crd clusterserviceversions.operators.coreos.com
kubectl delete crd installplans.operators.coreos.com
kubectl delete sa -n ibm-system olm-operator-serviceaccount
kubectl delete clusterrole system:controller:operator-lifecycle-manager
kubectl delete clusterrolebinding olm-operator-binding-ibm-system
kubectl delete clusterrole aggregate-olm-edit
kubectl delete clusterrole aggregate-olm-view

For instructions about how to install the new OLM framework, see [How do I install OLM?](https://operator-framework.github.io/olm-book/docs/install-olm.html).



Because private workers are not compatible with Red Hat OpenShift Pipelines, it is recommended that you do not install them on a cluster with Red Hat OpenShift pipelines.





 Installing a Delivery Pipeline Private Worker 

To install a private worker, you must have Administrator level access to a cluster. Private worker installation can be completed only by way of the command line since no graphical user interface is available.



 Installing the Delivery Pipeline Private Worker by using the CLI 

The following steps are intended for Administrators who are preparing environments and private workers for multiple people or teams. To install private workers for your own use, see [Setting up a Delivery Pipeline Private Worker](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-private-workersset_up_private_worker).
For more information, see [Version constraints for the Terraform providers](https://cloud.ibm.com/docs/schematics?topic=schematics-version-constraintsprovider-version-contraint).





 What is the difference between delete, and destroy in Schematics? 

Destroy delete the associated cloud resource from the workspace. Delete workspace is to used to delete the workspace. The recommendation is to destroy the resource first from the workspace, and then set delete workspace. For more information, see [Deleting a workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks)





 Can I delete and destroy operation as one step? 

No, you cannot [delete](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks) and [destroy](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-destroy-wks) operation in one step. You need to follow the [process](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks) to destroy first and then delete.





 What is a resource group and how does it help me organize my team? 

Assigning access to a particular IBM Cloud service is a good way of allowing a user to work with a specific service in your account. However, when you build production workloads in the cloud, you most likely have multiple IBM Cloud services and resources that are used by different teams. With resource groups, you can organize multiple services in your account and bundle them under one common view and billing process. To allow your team to work with these resources, you can assign IAM access policies to a resource group that allows them to view and manage the resources within a resource group.

For example, you have a team A that is responsible to manage an IBM Cloud Kubernetes Service cluster, and another team B that develops serverless apps with IBM Cloud® Functions.
For more information, see [Version constraints for the Terraform providers](https://cloud.ibm.com/docs/schematics?topic=schematics-version-constraintsprovider-version-contraint).
* What is the difference between delete, and destroy in Schematics?

Destroy delete the associated cloud resource from the workspace. Delete workspace is to used to delete the workspace. The recommendation is to destroy the resource first from the workspace, and then set delete workspace. For more information, see [Deleting a workspace](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks)
* Can I delete and destroy operation as one step?

No, you cannot [delete](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks) and [destroy](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-destroy-wks) operation in one step. You need to follow the [process](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-delete-wks) to destroy first and then delete.
* What is a resource group and how does it help me organize my team?

Assigning access to a particular IBM Cloud service is a good way of allowing a user to work with a specific service in your account. However, when you build production workloads in the cloud, you most likely have multiple IBM Cloud services and resources that are used by different teams. With resource groups, you can organize multiple services in your account and bundle them under one common view and billing process. To allow your team to work with these resources, you can assign IAM access policies to a resource group that allows them to view and manage the resources within a resource group.

For example, you have a team A that is responsible to manage an IBM Cloud Kubernetes Service cluster, and another team B that develops serverless apps with IBM Cloud® Functions.