vania-janet/multiturn-rag-retrieval-data huggingface dataset:
After you create your toolchain, you might need to adjust the pipeline scripts for your deployment goals.
* Create an empty toolchain, and then add tool integrations to deploy your app. For more information about using this method to deploy your code to Continuous Delivery, see [Continuous Deployment to Kubernetes](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-continuous-deployment-to-kubernetes).







 How do I find the status of IBM Cloud and the Continuous Delivery service? 

Check the IBM Cloud Status page to determine whether known issues are affecting the IBM Cloud platform and the major services in IBM Cloud.

You can find the Status page by choosing either of the following options:



* In the IBM Cloud console, go to Support. From the Today's notifications widget, click View all, and then click Status to view the status of resources in all IBM Cloud locations. You can view a list of events, in chronological order, for maintenance and incidents. You can search across all notifications, or filter by type, geographic locations, and individual resources. You can also view planned maintenance windows for which prior notice is provided and unplanned incidents or outages, which are posted as soon as the IBM Cloud team becomes aware of them. Incident notifications are regularly updated until they're resolved.
* Access it directly at [IBM Cloud - System Status](https://cloud.ibm.com/status).



For more information about the IBM Cloud Status page, see [Viewing IBM Cloud status](https://cloud.ibm.com/docs/get-support?topic=get-support-viewing-cloud-statusviewing-cloud-status).





 How do I remove authorized users from the Continuous Delivery service? 

You can remove authorized users from the Continuous Delivery service and prevent them from being added again.



* Remove the user's access in IAM to all toolchains in the resource group.
* Remove the user from the authorized user list in the Continuous Delivery service instance.
* Remove Developer access from all Git Repos and Issue Tracking repos that are attached to all of the toolchains in the resource group.



You can maintain an activity log related to authorized users.
Common problems 

Here are a few difficulties you might encounter.



 Not authorized (401 or 403 error) 

Your account might not be authorized for VPC. Make sure that you are using an account that has been onboarded.





 IAM token expired 

The service is no longer returning any JSON, instead of just giving an HTTP "401 Unauthorized" to all requests. This error occurs after about an hour if your IAM token has expired. Refresh your IAM token by rerunning iam_token=$(ibmcloud iam oauth-tokens | awk '/IAM/{ print $4; }').





 Cannot create resources 

If you cannot create a VPC or other resources, make sure that the owner of the account has granted you the correct [permissions](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-user-permissions-for-vpc-resourcesmanaging-user-permissions-for-vpc-resources).





 No response from API 

If the API is no longer returning any JSON, it is likely your IAM token has expired and needs to be refreshed. Log in to IBM Cloud again or refresh your token by running iam_token=$(ibmcloud iam oauth-tokens | awk '/IAM/{ print $4; }').







 Cannot delete resources 

Certain operations--creating and deleting virtual server instances, and creating and deleting subnets, for example--are completed asynchronously through the API. Because of this fact, it is recommended to poll the resources you're deleting, to check for deletion before proceeding.

It can take several minutes for resources to be deleted from the system, due to these asynchronous operations. To facilitate deletion, the best practice is to do things in this order:



1. Delete your instances
2. Delete your public gateways
3. Delete your subnets
4. Delete your VPCs
FAQs for Netezza Performance Server 

This is a collection of frequently asked questions (FAQ) about the IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service.



 How do I sign up for Netezza Performance Server? 

[Create a free IBM Cloud account](https://cloud.ibm.com/registration?target=%2Fcatalog%2Fservices%2Fdb2-warehouse). When you have the account, you can provision a Netezza Performance Server instance directly through the IBM Cloud® catalog.
For more information, see [Getting started with Netezza Performance Server](https://cloud.ibm.com/docs/netezza?topic=netezza-getstarted).





 How do I generate or view credentials for my Netezza Performance Server instance? 

To generate credentials, follow the steps:



1. Log in to [IBM Cloud](https://cloud.ibm.com/) account.
2. Go to Resource list > Services and Software > Databases.
3. Click on your Netezza Performance Server instance.
You are now on the Service instance details page.
4. Go to the Service Credentials tab.
5. Click New Credentials.
6. Type a name to assing to your credentials.
7. Select the IAM role that was assigned to you to manage the instance.
8. Click Add.
If your credentials were generated successfully, you can view them now. Expand your credential entry. The following credentials were generated:



* username: admin - Specifies a local database admin user that was created for you to access the instance.
* password: xxxx - Specifies the password that you must use when logging in to your instance as admin.



After you log in to your instance for the first time, change your admin password.



To view credentials, follow the steps:



1. Log in to [IBM Cloud](https://cloud.ibm.com/) account.
2. Go to Resource list > Services and Software > Databases.
3.
Added: IBM Cloud® Hyper Protect Virtual Servers Secure Build Server feature.
: You can now use IBM Cloud® Hyper Protect Virtual Servers Secure Build Server to securely build an image, which you then can use to provision a virtual server. For more information, see [Deploying the Secure Build Server as a Hyper Protect Virtual Server](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-imagebuilddeploysecurebuild).

Added: The tutorial about using the Secure Build Server with a digital wallet
: The tutorial "Using Secure Build Server with a digital wallet" is available. For more information, see [Tutorial: Using Secure Build Server with a digital wallet](https://cloud.ibm.com/docs/hp-virtual-servers?topic=hp-virtual-servers-tutorial_secure_build_server).





 24 February 2021 

The new parameter outbound is now available when you provision a server.





 12 October 2020 

You can provide environment variables when you provision and update servers using a custom OCI image.





 15 September 2020 

You can now update the OCI image that's used for your virtual server.





 08 August 2020 

The Hyper Protect Virtual Servers command line interface is upgraded to v1.0.1. to include security and other minor fixes together with improved error messages.





 27 July 2020 

The new Hyper Protect Virtual Servers command line interface is now available.





 06 July 2020 

Three new data centers are available for creating virtual servers: Washington 04, Washington 06, and Washington 07.





 14 April 2020 

Detailed information about enhancing security for Hyper Protect Virtual Servers is now available.





 26 March 2020 

The IBM Cloud command line interface can be used to list, create, or delete your Hyper Protect Virtual Servers instances.





 24 March 2020 

A virtual server now has a seven day reclamation period after you "delete" it from the resource list. During the reclamation period you can restore the virtual server or manually trigger a deletion via resource reclamations.





 27 February 2020 

A new pricing plan is available: Entry.





 30 January 2020
Make sure that your Terraform config files are compatible with the Terraform version that you specify. This is a required variable. If the Terraform version is not specified, By default, Schematics selects the version from your template. 
 description Optional Enter tags that you want to associate with your workspace. Tags can help you find your workspace faster. 
 resource_group Optional Enter the resource group where you want to provision your workspace. 
 workspace_status Optional Freeze or unfreeze a workspace. If a workspace is frozen, changes to the workspace are disabled. 
 template_repo.url Optional Enter the URL to the GitHub or GitLab repository where your Terraform configuration files are stored. 
 template_repo.branch Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. Now, in template repository, you can also update URL with more parameters as shown in the block. 
 template_repo.datafolder Optional Enter the name of the folder in the Git repository, that contains the template. 
 template_repo.release Optional Enter the GitHub or GitLab release that points to your Terraform configuration files. 
 github_source_repo_url Optional Enter the link to your GitHub repository. The link can point to the master branch, a different branch, or a subdirectory. 
 template_data.folder Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 template_data.type Optional Enter the name for the input variable type that you declared in your Terraform configuration files. 
 template_data[0].env_values[i].va11 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job. This field must be provided as a list of key-value pairs, for example, TF_LOG=debug. Each entry will be a map with one entry where key is the environment variable name and value is value. 
 template_data[0].env_values[i].val2 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job.
Make sure that your Terraform config files are compatible with the Terraform version that you specify. This is a required variable. If the Terraform version is not specified, By default, Schematics selects the version from your template. 
 description Optional Enter tags that you want to associate with your workspace. Tags can help you find your workspace faster. 
 resource_group Optional Enter the resource group where you want to provision your workspace. 
 workspace_status Optional Freeze or unfreeze a workspace. If a workspace is frozen, changes to the workspace are disabled. 
 template_repo.url Optional Enter the URL to the GitHub or GitLab repository where your Terraform configuration files are stored. 
 template_repo.branch Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. Now, in template repository, you can also update URL with more parameters as shown in the block. 
 template_repo.datafolder Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. 
 template_repo.release Optional Enter the GitHub or GitLab release that points to your Terraform configuration files. 
 github_source_repo_url Optional Enter the link to your GitHub repository. The link can point to the master branch, a different branch, or a subdirectory. 
 template_data.folder Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 template_data.type Optional Enter the name for the input variable type that you declared in your Terraform configuration files. 
 template_data[0].env_values[i].va11 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job. This field must be provided as a list of key-value pairs, for example, TF_LOG=debug. Each entry will be a map with one entry where key is the environment variable name and value is value. 
 template_data[0].env_values[i].val2 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job.
template_repo.branch Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. Now, in template repository, you can also update URL with more parameters as shown in the block. 
 template_repo.datafolder Optional Enter the GitHub or GitLab branch where your Terraform configuration files are stored. 
 template_repo.release Optional Enter the GitHub or GitLab release that points to your Terraform configuration files. 
 github_source_repo_url Optional Enter the link to your GitHub repository. The link can point to the master branch, a different branch, or a subdirectory. 
 template_data.folder Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 template_data.type Optional Enter the name for the input variable type that you declared in your Terraform configuration files. 
 template_data[0].env_values[i].va11 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job. This field must be provided as a list of key-value pairs, for example, TF_LOG=debug. Each entry will be a map with one entry where key is the environment variable name and value is value. 
 template_data[0].env_values[i].val2 Optional A list of environment variables that you want to apply during the execution of a bash script or Terraform job. This field must be provided as a list of key-value pairs, for example, TF_LOG=debug. Each entry will be a map with one entry where key is the environment variable name and value is value. 
 template_data[0].env_values_metadata Optional Environment variables metadata. 
 template_data[0].variablestore[i].name Optional Enter the name for the input variable that you declared in your Terraform configuration files. 
 template_data[0].variablestore[ii].type Required Terraform v0.12 supports string, list, map, bool, number and complex data types such as list(type), map(type), object({attribute name=type,..
[Action menu icon](https://cloud.ibm.com/docs-content/v1/content/4d497aff9e27b92fbbc2ee4e343a9ec4549cb1d7/icons/action-menu-icon.svg)> Remove user.
4. When IBM Cloud IAM platform permissions are removed, the user's permissions are also automatically removed from the associated predefined RBAC roles. To update the RBAC roles with the changes, run ibmcloud ks cluster config. However, if you created [custom RBAC roles or cluster roles](https://cloud.ibm.com/docs/containers?topic=containers-usersrbac), you must remove the user from the .yaml files for those RBAC role bindings or cluster role bindings. See steps to remove custom RBAC permissions in the next section.







 Remove custom RBAC permissions 

If you don't need custom RBAC permissions anymore, you can remove them.



1. Open the .yaml file for the role binding or cluster role binding that you created.
2. In the subjects section, remove the section for the user.
3. Save the file.
4. Apply the changes in the role binding or cluster role binding resource in your cluster.

kubectl apply -f my_role_binding.yaml







 Remove Cloud Foundry permissions 

To remove all Cloud Foundry permissions for a user, you can remove the user's organization roles. If you want to remove only a user's ability, for example, to bind services in a cluster, then remove only the user's space roles.



1. Log in to the [IBM Cloud console](https://cloud.ibm.com/). From the menu bar, select Manage > Access (IAM).
2. Click the Users page, and then click the name of the user that you want to remove permissions from.
3. Click the Cloud Foundry access tab.



* To remove the user's space role



1. Expand the table entry for the organization that the space is in.
Who enforces that only one public gateway can exist per zone for a VPC? 

The VPC API service enforces this limit.





 Does the VPC public gateway have a timeout function? 

Yes, the VPC public gateway has a fixed, 4-minute timeout for TCP connections, and it is not configurable.





 How do you obtain the Cloud Resource Name (CRN) of a VPC? 

To obtain the CRN of a VPC, click menu![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/icon_hamburger.svg) > Resource list from the IBM Cloud console. Expand VPC Infrastructure to list your VPCs. Select a VPC and then click the Status entry to view its details. Use the icon to copy the CRN and paste it where needed.
To stay in synchronize with your Terraform template, make sure to remove the associated infrastructure code from your Terraform template. So that, your resources are not added again when you apply a new version of your Terraform template.
* What happens if I choose to delete my resource directly from the resource dashboard?

When you manually remove a resource that you provisioned with IBM Cloud Schematics, the state file is not updated automatically and becomes out of sync. When you create next Terraform execution plan, or apply a new template version. The Schematics verifies that the IBM Cloud resources in the state file exist in your IBM Cloud account with the state that is captured. If the resource is not found, the state file is updated, and the Terraform execution plan is changed.

Although the state file is updated before new changes to your IBM Cloud resources are applied, do not manually remove resources from the resource dashboard to avoid unexpected results. Instead, use the IBM Cloud Schematics console or CLI to remove your resources, or remove the associated infrastructure code from your Terraform template.
* Does Schematics supports ibmcloud terraform command?

Using ibmcloud terraform command from CLI release v1.8.0 displays a warning message as Alias Terraform are deprecated. Use schematics or sch in your commands. For more information, see [CLI version history](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases).
* Can I access private network through Schematics?

Yes, from [CLI release v1.8.0](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) Schematics supports private Schematics endpoint to access your private network. For more information, see [private Schematics endpoint](https://cloud.ibm.com/docs/schematics?topic=schematics-private-endpointsprivate-cse).
* How can I resolve the error message when connecting to Bastion host IP addresses through IBM Cloud Schematics?

Error:
* UI
* CLI
* API







 Removing context-based restrictions 

By removing context-based restrictions, you delete restrictions that are defined by the contexts in a rule. Deleting rules removes context-based restrictions from the given resource, and requests from any context are allowed if the user has the correct permissions.



 Removing a rule 

You can remove a rule on your cloud resources by completing the following steps:



1. In the IBM Cloud console, go to Manage > Context-based restrictions, and select Rules.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) in the row that contains the rule, and click Remove.







 Removing a rule by using the CLI 

You can remove a rule on your cloud resources by completing the following steps:



1. Retrieve the rule ID for the rule that you want to delete by using the [context-based restrictions rules](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-rules-command) command. You can narrow the results of the list by specifying attributes as command options.

ibmcloud cbr rules --serviceName "iam-identity"
2. Delete the rule for the specified rule ID by using the [cbr rule-delete](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-rule-delete-command) command.

ibmcloud cbr rule-delete 30fd58c9b75f40e854b89c432318b4a2







 Removing a rule by using the API 

You can remove a rule on your cloud resources by completing the following steps:



1.
* UI
* CLI
* API







 Removing context-based restrictions 

By removing context-based restrictions, you delete restrictions that are defined by the contexts in a rule. Deleting rules removes context-based restrictions from the given resource, and requests from any context are allowed if the user has the correct permissions.



 Removing a rule 

You can remove a rule on your cloud resources by completing the following steps:



1. In the IBM Cloud console, go to Manage > Context-based restrictions, and select Rules.
2. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/d4595e5202a9a27767cf034e81b038cdf772e0d5/secure-enterprise/includes/account/includes/icons/action-menu-icon.svg) in the row that contains the rule, and click Remove.







 Removing a rule by using the CLI 

You can remove a rule on your cloud resources by completing the following steps:



1. Retrieve the rule ID for the rule that you want to delete by using the [context-based restrictions rules](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-rules-command) command. You can narrow the results of the list by specifying attributes as command options.

ibmcloud cbr rules --serviceName "iam-identity"
2. Delete the rule for the specified rule ID by using the [cbr rule-delete](https://cloud.ibm.com/docs/account?topic=cli-cbr-plugin&interface=clicbr-cli-rule-delete-command) command.

ibmcloud cbr rule-delete 30fd58c9b75f40e854b89c432318b4a2







 Removing a rule by using the API 

You can remove a rule on your cloud resources by completing the following steps:



1.
To stay in synchronize with your Terraform template, make sure to remove the associated infrastructure code from your Terraform template. So that, your resources are not added again when you apply a new version of your Terraform template.





 What happens if I choose to delete my resource directly from the resource dashboard? 

When you manually remove a resource that you provisioned with IBM Cloud Schematics, the state file is not updated automatically and becomes out of sync. When you create next Terraform execution plan, or apply a new template version. The Schematics verifies that the IBM Cloud resources in the state file exist in your IBM Cloud account with the state that is captured. If the resource is not found, the state file is updated, and the Terraform execution plan is changed.

Although the state file is updated before new changes to your IBM Cloud resources are applied, do not manually remove resources from the resource dashboard to avoid unexpected results. Instead, use the IBM Cloud Schematics console or CLI to remove your resources, or remove the associated infrastructure code from your Terraform template.





 Does Schematics supports ibmcloud terraform command? 

Using ibmcloud terraform command from CLI release v1.8.0 displays a warning message as Alias Terraform are deprecated. Use schematics or sch in your commands. For more information, see [CLI version history](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases).





 Can I access private network through Schematics? 

Yes, from [CLI release v1.8.0](https://cloud.ibm.com/docs/schematics?topic=schematics-cli_version-releases) Schematics supports private Schematics endpoint to access your private network. For more information, see [private Schematics endpoint](https://cloud.ibm.com/docs/schematics?topic=schematics-private-endpointsprivate-cse).





 How can I resolve the error message when connecting to Bastion host IP addresses through IBM Cloud Schematics? 

Error:

timeout - last error: Error connecting to bastion: dial tcp