vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Where is the Terraform state file stored? 

After you successfully provisioned IBM Cloud resources by running a Schematics apply action, the state of resources is stored in a Terraform state file (terraform.tfstate). Schematics uses this state file as the single source of truth to determine what resources exist in your account. The state file maps the resources that you specified in your Terraform configuration file to the IBM Cloud resource that you provisioned.





 Are resources removed on delete workspace? 

Deleting a workspace from IBM Cloud Schematics does not remove any of your IBM Cloud resources. If you delete the workspace before you remove your resources, you must manually remove all your IBM Cloud resources from the individual resource dashboard.

Removing IBM Cloud resources cannot be undone. Make sure that you have backed up any data before you remove a resource. Resources will also be removed(deleted) if you remove the resource definition or comment out the resource in your Terraform configuration file. Review the Plan log file to verify that all your resources are included in the removal.





 Can I set environment variables for workspaces? 

You can set env values for a workspace using the CLI and API. For more information, see [usage of env_values](https://cloud.ibm.com/docs/schematics?topic=schematics-set-parallelism).

Sample payload:

{
"name": "newName",
"template_data": [
{
"type": "<same_as_before>",
"env_values":
{
"env_values_1": "dummy_text"
},
{
"env_values_2": "dummy_text"
}
],
"env_values_metadata":
{
"name": "env_values_1",
"hidden": false,
"secure": false
},
{
"name": "env_values_2",
"hidden": false,
"secure": false
}
]
}
For example, if you move an instance from the state, the Schematics Workspaces instance continues running, but Terraform plan cannot see that instance. You can use the workspace ID to retrieve the logs by using the [ibmcloud schematics logs](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-logs) command.

ibmcloud schematics workspace state mv --id WORKSPACE_ID --source SOURCE --destination DESTINATION

Command options



Schematics state move flags

 Flag Required / Optional Description 

 --id or -i Required The unique ID of the workspace for which you want to move an instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --source or -s Required Enter the source address of an item to move. 
 --destination or -d Required Provide the destination address of an item. 



Example

ibmcloud schematics workspace state mv --id myworkspace-a1aa1a1a-a11a-11 -s testsourceresource -d null_resource.sleep





 ibmcloud schematics workspace state rm 

Removes an instance or resources from the Terraform state. For example, if you remove an instance from the state, the Schematics Workspaces instance continues running, but Terraform plan cannot see that instance. You can use the workspace ID to retrieve the logs by using the [ibmcloud schematics logs](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-logs) command.

ibmcloud schematics workspace state rm --id WORKSPACE_ID [--options OPTIONS] --address PARAMETER

Command options



Schematics state remove flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace for which you want to remove the instance or resource. To find the ID of your workspace, run ibmcloud schematics workspace list command.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/speech-to-text?topic=speech-to-text-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/language-translator?topic=language-translator-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/discovery?topic=watson-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/natural-language-understanding?topic=watson-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/watson-knowledge-studio?topic=watson-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
If you see a drop-down menu flash and disappear, check that you have correctly followed sub-step 5 of [Step 3. Grant service access](https://cloud.ibm.com/docs/watson?topic=watson-keyserviceserviceauth-key)
6. Click Create.



The data that is associated with this Watson service instance is now encrypted.







 Working with customer-managed keys 

After you enable a customer-managed key, the service operates normally, and you can manage access to the data with Key Protect.



 Temporarily prevent access to your data 

To temporarily prevent access, remove all authorizations between the Watson service and Key Protect:



* Remove the authorization that you created in Step 3 from the IAM [Authorizations](https://cloud.ibm.com/iam/authorizations) page.
* Remove all other authorizations between other services connected with the Watson service and Key Protect.



1. Find the Cloud Resource Name identifier (CRN) for the Watson service that you want to remove access to. You find the CRN by clicking the service instance row in your [Resource list](https://cloud.ibm.com/resources?groups=resource-instance). The CRN is displayed in the details pane.
2. Back on the Authorizations page, search for that CRN in the list.
3. Remove every authorization with the CRN of the Watson service as the source and Key Protect as the target.



These other authorizations might exist because the Watson service can create delegated policies from the authorization that you created.



The Watson instance can no longer access the data because no authorizations exist to access the key. For more information, search for [Removing an authorization](https://cloud.ibm.com/docs/account?topic=account-serviceauthremove-auth) in "Using authorizations to grant access between services".





 Restore temporary access 

To restore access after you temporarily remove it, follow these steps:



1. Re-create the authorization between your Watson service and Key Protect instance as shown in [Step 3.
Cloud Backup Portal is only accessible through [IBM Cloud® VPN](https://www.ibm.com/cloud/vpn-access).
5. On the navigation, click Computers. The computers page shows the registered computers and environments. Expand the computer that you want to back up to a second vault.
6. Click Vault Settings.
7. In the Vault Settings window, click Add Vault.
8. In the New Vault window,



1. In the Vault Profile menu, choose Enter Vault Settings to create a new entry. Don't update the existing entry, it doesn't work.
2. The vault name can't be the same as the other vault name. Try adding a -2 tag to the end of it.

The vault name field has a 15 character limit.
3. In the IP address field, add the address of the second IBM Cloud Backup for Classic vault location.

You can look up the fully qualified domain name of the IBM Cloud Backup for Classic vault in the [IBM Cloud console](https://cloud.ibm.com/login). You can either use the FQDN or the IP address of the server to connect to the vault. To get the IP address, ping the FQDN from the server that's going to be backed up. For example, if you want to connect to the vault in a data center located in Dallas, you can use ev-vaultdal1201.service.softlayer.com or its IP address 10.200.134.250.
4. In the credentials field, enter the account ID, the IBM Cloud Backup for Classic username for the selected vault, and the password for the selected vault. For more information about viewing the username or changing the backup password, see [Managing username and password for the Cloud Backup service](https://cloud.ibm.com/docs/Backup?topic=Backup-changePassword).
5. Click Save.





In a few seconds, the new vault is usable. If you get a connection failure, check your settings, and try again.
For more information, see [Using resource reclamations](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).

When you delete an access management tag from the account, any associated IAM policies are also deleted with it.





 How do I view my dashboard role? 

You can view the role that you are assigned on a dashboard by going to Manage > Account > Dashboards in the IBM Cloud console. All users besides the dashboard owner have the viewer role on the dashboard.





 Can I edit the default dashboard? 

You can't edit the default dashboard directly. However, you can create a duplicate version that you can edit and personalize however you want by clicking the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Edit in IBM Cloud console.

By maintaining the original version of the default dashboard, you can discover the latest widgets and functionalities, which get built and added over time. This way, you can always bring out the most of your workflow.

You can also switch between the duplicate and original versions by selecting each one from your list of dashboards that's displayed on your active dashboard.





 Can I move an org to another account? 

Currently, you can't move an org to a different account. However, you can re-create the org with the same credentials in a different account to mimic this functionality. For more information, see [Adding orgs and spaces](https://cloud.ibm.com/docs/account?topic=account-orgsspacesuserscreateorg).





 Why do I get logged out of my account? 

The administrator of your account has customized the duration of active and inactive accounts, which requires users to enter their credentials after a specific time. For more information, see [Managing user's login session durations](https://cloud.ibm.com/docs/account?topic=account-iam-work-sessions).
Why am I getting an authentication failure when logging in to my Azure Disk or Azure File Satellite configuration? 

  What’s happening 

You are unable to access your storage configuration due to an authentication error.

  How to fix it 

Verify that your service principal is configured correctly.

To view your service principal configuration, follow the steps in the [Azure CLI documentation](https://docs.microsoft.com/en-us/cli/azure/create-an-azure-service-principal-azure-cli2-get-an-existing-service-principal).
* [kubectl commands don't work](https://cloud.ibm.com/docs/containers?topic=containers-ts_cliskubectl_fails)
* [kubectl commands time out](https://cloud.ibm.com/docs/containers?topic=containers-ts_clisexec_logs_fail)



[Why can't I create or delete clusters or worker nodes?](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorscluster_infra_errors)



* [Unable to create or delete worker nodes due to permission errors](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorscs_credentials)
* [Unable to create or delete worker nodes due to incorrect account error](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorsorphaned)
* [Unable to create or delete worker nodes due to endpoints error](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorsvpe-ts)
* [Unable to create or delete worker nodes due to paid account or one time password error](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorscs_totp)



* [Disabling TOTP MFA for the account](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorsdisable-totp-mfa-account)
* [Using TOTP MFA to create an infrastructure API key for IBM Cloud Kubernetes Service](https://cloud.ibm.com/docs/containers?topic=containers-cluster_infra_errorscreate-api-key-totp-mfa)





[VPC: Why is no VPC available when I create a cluster in the console?](https://cloud.ibm.com/docs/containers?topic=containers-ts_no_vpcts_no_vpc)