vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud schematics workspace action --id WORKSPACE_ID [--act-id ACTION_ID] [--output OUTPUT]

Command options



Schematics Workspaces action flags

 Flag Required / Optional Description 

 --id or -i Required The unique identifier of the workspace for which you want to retrieve workspace activities. To find the ID of your workspace, run ibmcloud schematics workspace list command. 
 --act-id or -a Optional Enter the ID of a action that you want to retrieve. 
 --json or -j Deprecated Prints the output in the JSON format. 
 --output or -o Optional Returns the command-line output in JSON format. Currently only JSON file format is supported. 



Example

ibmcloud schematics workspace action --id myworkspace-a1aa1a1a-a11a-11





 ibmcloud schematics workspace delete 

Delete a workspace from your IBM Cloud account. The deletion of your workspace does not remove any IBM Cloud resources that you provisioned with this workspace. You can access and work with your resources from the IBM Cloud dashboard directly, but you cannot use IBM Cloud Schematics to manage your resources after you delete the workspace.

IBM Cloud Schematics supports 50 API requests per minute, per host, and per customer. The host can be us-east, us-south, eu-gb, or eu-de region. You need to wait before calling the command again. The table describes the delete workspace and destroy resources with the action.

Decide if you want to delete the workspace, any associated resources, or both. This action cannot be undone. If you remove the workspace and keep the resources, you need to manage the resources with the resource list or CLI.



delete workspace and associated resource

 Action Delete workspace Delete all associated resources 

 Delete workspace True False 
 Delete only resources False True 
 Delete workspace and the resources provisioned by workspace True True 
 Resources destroyed using command-line or resource list, and want to delete workspace True False 



Syntax
Managing dedicated hosts and groups 

With a dedicated group and dedicated host created, you can manage your resources. You can create additional dedicated hosts, provision new virtual server instances, or delete resources. You can also disable placement of new instances on a dedicated host. Disabling placement of new instances is required if you need to delete a dedicated host.



 Managing dedicated hosts 

When you have a dedicated host created, you can create new virtual server instances on the host or disable placement of instances on the host. If you no longer need a dedicated host or dedicated group, you can delete the resources.

To complete management tasks on your dedicated hosts, complete the following steps.



1. In the [IBM Cloud console](https://cloud.ibm.com/vpc-ext), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Dedicated hosts.
2. On the Dedicated hosts tab of the Dedicated hosts for VPC page, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for the dedicated host that you want to manage. You can select from the following actions:





Table 1. Actions available for dedicated hosts

 Action Description 

 New instance Create a virtual server instance on this dedicated host. 
 Disable placement Temporarily prevent new virtual server instances from being provisioned on this host. No instances can be created on the host until placement is enabled again. You must disable placement before you can delete a dedicated host. 
 Enable placement Indicate that new virtual server instances can be provisioned on this host. If placement has been disabled, it must be enabled before instances can be created on the host.
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/fcee192e52fce225776143bc6ccc3a023d1d193a/databases-for-etcd/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI
When this happens, the Analyze API returns null results (see example) and the stateless api rest proxy will display this message in its log: RESOURCE_EXHAUSTED: stateless.Analysis/analyze: RESOURCE_EXHAUSTED.
{
"result": null,
"notices": null
}

To work around this issue:

<-- <ol> -->

1. Review the enrichments used in the collection and remove those that are not necessary for your application. In particular, remove the Part of Speech enrichment.
2. Reduce the number of collections used concurrently with the Analyze API.
3. Increase the cache memory:

<-- <ul> -->

* Increase the memory limit of container model-runtime in deployment core-discovery-stateless-api-model-runtime to 10 GB or more
* Edit the environment variable CAPACITY_MB in deployment core-discovery-stateless-api-model-runtime, set it to 10240 or more

<-- </ul> -->

<-- </ol> -->

* If the model runtime container is restarted but the model mesh runtime container is not, the Analyze API can run into problems.
<-- <ul> -->

* Error: The Analzye API call returns 500 error on a specific collection and the log contains the following entry:

"message": "error occurred in analyzer
java.lang.NullPointerException
at c.i.e.a.a.s.r.ModelManager$2.analyze(ModelManager.java:112)
* Cause: The model runtime container and model mesh runtime container are out of sync.
* Solution: Delete the wd-stateless-api-model-runtime pods to restart both the model mesh and model runtime containers.

<-- </ul> -->
To list versions in your configuration, run ibmcloud sat config get --config <configuration_name_or_ID>.

--output JSON
: Optional. Displays the command output in JSON format.

--save-config
: Optional. Download and save the Kubernetes resource configuration file of the version to a temporary file.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat config version get --config myapp_prod --version 1.0







 ibmcloud sat config version rm 

Remove a version from your Satellite configuration.

ibmcloud sat config version rm --config CONFIG --version VERSION [-f] [-q]



 Minimum required permissions 

IBM Cloud IAM Editor platform role for the Configuration resource in Satellite. For more information, see [Checking user permissions](https://cloud.ibm.com/docs/satellite?topic=satellite-iam-assign-accesschecking-perms).





 Command options 

--config CONFIG
: Required. The name or ID of the configuration where you want to remove a version. To list available configurations, run ibmcloud sat config ls.

--version VERSION
: Required. The name or ID of your version. To list versions in your configuration, run ibmcloud sat config get --config <configuration_name_or_ID>.

-f
: Optional. Force the command to run with no user prompts.

-q
: Optional. Do not show the message of the day or update reminders.





 Example 

ibmcloud sat config version rm --config myapp_prod --version 1.0









 Endpoint commands 

Use these commands to create and manage Satellite Link endpoints to allow network traffic between your IBM Cloud Satellite® location and services, servers, or apps that run in IBM Cloud.



 ibmcloud sat endpoint create 

Create a Satellite endpoint.
curl -fSsL https://install.portworx.com/px-wipe | bash -s -- --talismanimage icr.io/ext/portworx/talisman --talismantag 1.1.0 --wiperimage icr.io/ext/portworx/px-node-wiper --wipertag 2.5.0
2. Find the installation name of your Portworx Helm chart.

helm ls -A | grep portworx

Example output

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
<release_name> <namespace> 1 2020-01-27 09:18:33.046018 -0500 EST deployed portworx-1.0.0 default
3. Delete Portworx by removing the Helm chart.

helm uninstall <release_name>
4. Verify that the Portworx pods are removed.

kubectl get pod -n kube-system | grep 'portworx|stork'

The removal of the pods is successful if no pods are displayed in your CLI output.
5. Delete the Portworx storage classes from your cluster.

kubectl delete sc portworx-db-sc portworx-db-sc-remote portworx-db2-sc portworx-null-sc portworx-shared-sc
6. Verify that the storage classes are removed.

kubectl get sc
7. Verify that the Portworx resources are removed.

kubectl get all -A | grep portworx
8. Remove the Portworx service instance from your IBM Cloud account.



1. From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
2. From the actions menu, click Delete.
3. Confirm the deletion of the service instance by clicking Delete.
The four files are: certificate file, certificate signing request file, intermediate certificate file, and private key file.





 ibmcloud sl security cert-list 

List SSL certificates on your account:

ibmcloud sl security cert-list [OPTIONS]

Command options:

--status
: Show certificates with this status, default is: all, options are: all,valid,expired.

--sortby
: Column to sort by. Options are: id,common_name,days_until_expire,note.

Examples:

ibmcloud sl security cert-list --status valid --sortby days_until_expire

This command lists all valid certificates on current account and sort them by validity days.





 ibmcloud sl security cert-remove 

Remove SSL certificate:

ibmcloud sl security cert-remove IDENTIFIER [OPTIONS]

Command options:

-f, --force
: Force operation without confirmation.

Examples:

ibmcloud sl security cert-remove 12345678

This command removes certificate with ID 12345678.
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 4. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in Activity Tracker Event Routing processing.
* [Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-iam)



To get started, check out the [best practices for access management and how to define access groups](https://cloud.ibm.com/docs/account?topic=account-account_setupresource-group-strategy).





 Remove resources 

To remove the resource, delete the deployed container and then the provisioned services.

If you share an account with other users, always make sure to delete only your own resources.



1. Delete the deployed container:

kubectl delete -f secure-file-storage.yaml
2. Delete the secrets for the deployment:

kubectl delete secret secure-file-storage-credentials
3. In the [IBM Cloud Resource List](https://cloud.ibm.com/resources) locate the resources that were created for this tutorial. Use the search box and secure-file-storage as pattern. Delete each of the services by clicking on the context menu next to each service and choosing Delete Service. Note that the Key Protect service can only be removed after the key has been deleted. Click on the service instance to get to the related dashboard and to delete the key.



Depending on the resource it might not be deleted immediately, but retained (by default for 7 days). You can reclaim the resource by deleting it permanently or restore it within the retention period. See this document on how to [use resource reclamation](https://cloud.ibm.com/docs/account?topic=account-resource-reclamation).





 Related content 



* [Security to safeguard and monitor your cloud apps](https://www.ibm.com/cloud/garage/architectures/securityArchitecture)
* [IBM Cloud Platform security](https://cloud.ibm.com/docs/overview?topic=overview-securitysecurity)
* [Security in the IBM Cloud](https://www.ibm.com/cloud/security)
roles: policyRoles,
resources: policyResources,
};

iamPolicyManagementService.createPolicy(params)
.then(res => {
examplePolicyId = res.result.id;
console.log(JSON.stringify(res.result, null, 2));
})
.catch(err => {
console.warn(err)
});

Not all services support policies at the resourceType and individual resource level. Examples of services that do support these attributes are IBM Cloud Object Storage and IBM Key Protect, where buckets and keys are the resource type and the ID is listed to specify the specific resource.





 Removing an authorization in the console 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service. If you remove any access policies created by the source service for its dependent services, the source service is unable to complete the workflow or access the target service.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Authorizations.
2. Identify the row for the authorization that you want to remove from the account.
3. Click the Actions icon ![Actions icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/action-menu-icon.svg) > Remove.
4. Select Remove.



If the source service is removed from the account, any policies that are created by that service for its dependent services are deleted automatically. Similarly, if the dependent service is removed from the account, any access policies that are delegated to that service are also deleted.





 Removing an authorization by using the CLI 

You can remove any authorization between services in the account if you are assigned the Administrator role on the target service. If you remove any access policies created by the source service for its dependent services, the source service is unable to complete the workflow or access the target service.
* UI
* CLI







 Deleting your Deployment and Removing your Data 

IBM Cloud® Databases instances are softly deleted in production when you delete or deprovision the instance in IBM Cloud.

IBM Cloud keeps the deployment in the soft delete state for three days before it issues a delete. The soft delete state addresses use cases when you accidentally delete an instance. You can re-enable an existing soft-deleted instance on your own.

Because a soft delete is essentially a disablement, no IBM Cloud® Databases for DataStax deployment can recover from a soft delete. Once an IBM Cloud® Databases for DataStax deployment is deleted, that deployment must be restored from a backup.



 Deleting your Deployment in the User Interface 

To delete your deployment instance from the Resource list section dashboard of the IBM Cloud dashboard, select your deployment. Next, by using the stacked three-dot menu icon ( ![Stacked three dots icon](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/includes/cloud-databases/includes/cloud-databases/images/stacked-three-dots.png) ), choose Delete from the drop list.

Zoom

![List of service instances on the Resource List](https://cloud.ibm.com/docs-content/v1/content/c1b02d6157702384a9668d8c58bb951e69117793/databases-for-redis/includes/cloud-databases/includes/cloud-databases/images/softdelete-ui-instance.png)

Figure 1. List of service instances on the Resource List





 Deleting your Deployment by using the CLI
* A 5xx response usually indicates an internal system error.



See the following table for some HTTP response codes:



Table 3. List of HTTP response codes

 Status code Status Description 

 200 OK The request was successful. 
 201 OK The request was successful. A resource is created. 
 400 Bad Request The request was unsuccessful. You might be missing a parameter that is required. 
 401 Unauthorized The IAM token that is used in the API request is invalid or expired. 
 403 Forbidden The operation is forbidden due to insufficient permissions. 
 404 Not Found The requested resource doesn't exist or is already deleted. 
 429 Too Many Requests Too many requests hit the API too quickly. 
 500 Internal Server Error Something went wrong in IBM Cloud Activity Tracker Event Routing processing.
curl -fSsL https://install.portworx.com/px-wipe | bash -s -- --talismanimage icr.io/ext/portworx/talisman --talismantag 1.1.0 --wiperimage icr.io/ext/portworx/px-node-wiper --wipertag 2.5.0
2. Find the installation name of your Portworx Helm chart.

helm ls -A | grep portworx

Example output

NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
<release_name> <namespace> 1 2020-01-27 09:18:33.046018 -0500 EST deployed portworx-1.0.0 default
3. Delete Portworx by removing the Helm chart.

helm uninstall <release_name>
4. Verify that the Portworx pods are removed.

oc get pod -n kube-system | grep 'portworx|stork'

The removal of the pods is successful if no pods are displayed in your CLI output.
5. Delete the Portworx storage classes from your cluster.

oc delete sc portworx-db-sc portworx-db-sc-remote portworx-db2-sc portworx-null-sc portworx-shared-sc
6. Verify that the storage classes are removed.

oc get sc
7. Verify that the Portworx resources are removed.

oc get all -A | grep portworx
8. Remove the Portworx service instance from your IBM Cloud account.



1. From the [IBM Cloud resource list](https://cloud.ibm.com/resources), find the Portworx service that you created.
2. From the actions menu, click Delete.
3. Confirm the deletion of the service instance by clicking Delete.
Use the --all-resource-groups option to list the SSH keys for all available resource groups. Optionally, you can filter the list to include only SSH keys for a specific resource group. Specify the resource group by using the RESOURCE_GROUP_ID or RESOURCE_GROUP_NAME variable. For more information, see [ibmcloud is keys](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencekeys-list).

ibmcloud is keys [--all-resource-groups]





 Listing all your SSH keys by using the API 

To list all SSH keys by using the API, use [List all keys](https://cloud.ibm.com/apidocs/vpc/latestlist-keys).

curl -X GET "$vpc_api_endpoint/v1/keys?version=2023-03-30&generation=2" -H "Authorization: Bearer $iam_token"





 Viewing the details of your SSH key by using the UI 

You can view the following details of an SSH key.



* Name
* Resource group
* Fingerprint
* Type
* Length
* Created date (Local)



To view details for an SSH key, complete the following steps.



1. In [IBM Cloud console](https://cloud.ibm.com/login), go to menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > SSH keys.
2. On the SSH keys for VPC page, a list of all existing SSH keys is displayed.
3. From the Actions menu, you can Rename or Delete the SSH key.







 Viewing the details of your SSH key by using the CLI 

You can view the name of the key and the ID of the key by using the ibmcloud is key command.
Select your cluster and click Delete from the More actions menu.



* From the IBM Cloud CLI



1. List the available clusters.

ibmcloud oc cluster ls
2. Delete the cluster.

ibmcloud oc cluster rm --cluster <cluster_name_or_ID>





3. Follow the prompts and choose whether to delete cluster resources, which include containers, pods, bound services, persistent storage, and secrets.



* Persistent storage: If you [dynamically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsdynamic_provisioning) storage with a storage class that sets reclaimPolicy: Delete, your persistent volume claim (PVC), persistent volume (PV), and the storage instance are automatically deleted when you delete the cluster. However, depending on when you delete the cluster, you might still see your storage instance in the IBM Cloud console for up to 72 hours or until the new billing cycle begins.

For storage that was [statically provisioned](https://cloud.ibm.com/docs/openshift?topic=openshift-kube_conceptsstatic_provisioning), or storage that you provisioned with a storage class that sets reclaimPolicy: Retain, the PVC and the PV are removed when you delete the cluster, but your storage instance and your data remain. You are still charged for your storage instance.

To manually remove the storage and find frequently asked questions about storage removal, review the documentation for each storage type in the links in the Before you begin section.





Next steps:



* After it is no longer listed in the available clusters list when you run the ibmcloud oc cluster ls command, you can reuse the name of a removed cluster.
* Classic clusters only: If you kept the subnets, you can [reuse them in a new cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-subnetssubnets_custom) or manually delete them later from your IBM Cloud infrastructure portfolio.
To provision the resources:



1. Change to the terraform script folder:

cd $CHECKOUT_DIR/vpc-app-deploy/tf
2. Initialize Terraform:

terraform init
3. Apply the Terraform plan:

terraform apply
4. View the output generated by the plan:

terraform output







 Test the configuration of the virtual servers 

Now that Terraform has deployed resources, you can validate they were correctly provisioned.



1. Validate that the frontend virtual server instance is reachable and has outbound access to the Internet:

../test_provision.bash $(terraform output -raw FRONT_IP_ADDRESS) INTERNET hi

The command output should be:

success: httpd default file was correctly replaced with the following contents:
INTERNET
success: provision of file from on premises worked and was replaced with the following contents:
hi
2. Validate that the backend can be reached through the bastion host and does not have access to the internet:

../test_provision.bash $(terraform output -raw BACK_NIC_IP) ISOLATED hi "ssh -F ../../scripts/ssh.notstrict.config root@$(terraform output -raw FRONT_NIC_IP) -o ProxyJump=root@$(terraform output -raw BASTION_IP_ADDRESS)"

The command output should be:

success: httpd default file was correctly replaced with the following contents:
ISOLATED
success: provision of file from on premises worked and was replaced with the following contents:
hi







 Remove resources 



1. Remove the resources created by Terraform:

terraform destroy









 Step 4: Installing software with Ansible 

[Ansible](https://www.ansible.com/) is a configuration management and provisioning tool, similar to [Chef](https://www.chef.io/products/chef-infra/) and [Puppet](https://puppet.com/), and is designed to automate multitier app deployments and provisioning in the cloud.