vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --volume-attach '[{"volume": {"id":"67531475-bd8a-478e-bcfe-2e53365cd0aa"}}]' Create instance with existing volume in volume attachment.
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --keys 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8,72b27b5c-f4b0-48bb-b954-5becc7c1dcb3 Create instance with multiple SSH keys.
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --dedicated-host c019b1f7-c4d6-430c-aaa4-e0cc25d47277 Create instance to be placed in the wanted dedicated host.
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --dedicated-host-group a4738ceb-5e59-4601-849a-61d7895740ee Create instance to be placed in the wanted dedicated host group.
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --placement-group 1d2afa0f-b9f2-4d85-ae35-a08885269644 Create instance to be placed in the wanted placement group.
Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. To get the zones that you need new VLAN IDs for, note the Location in the following command output. Note: If your cluster is a multizone, you need VLAN IDs for each zone.

ibmcloud oc cluster ls
2. Get a new private and public VLAN for each zone that your cluster is in by [contacting IBM Cloud support](https://cloud.ibm.com/docs/vlans?topic=vlans-ordering-premium-vlansordering-premium-vlans).
3. Note the new private and public VLAN IDs for each zone.
4. Note the name of your worker pools.

ibmcloud oc worker-pool ls --cluster <cluster_name_or_ID>
5. Use the zone network-set[command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_zone_network_set) to change the worker pool network metadata.

ibmcloud oc zone network-set --zone <zone> --cluster <cluster_name_or_ID> -- worker-pool ls <worker-pool> --private-vlan <private_vlan_ID> --public-vlan <public_vlan_ID>
6. Multizone cluster only: Repeat Step 5 for each zone in your cluster.
7. Rebalance or resize your worker pool to add worker nodes that use the new VLAN IDs. For example:

ibmcloud oc worker-pool resize --cluster <cluster_name_or_ID> --worker-pool <worker_pool> --size-per-zone <number_of_workers_per_zone>
8. Verify that your worker nodes are created.

ibmcloud oc worker ls --cluster <cluster_name_or_ID> --worker-pool <worker_pool>
Set the context for your cluster.](https://cloud.ibm.com/docs/containers?topic=containers-access_cluster)



1. To get the zones that you need new VLAN IDs for, note the Location in the following command output. Note: If your cluster is a multizone, you need VLAN IDs for each zone.

ibmcloud ks cluster ls
2. Get a new private and public VLAN for each zone that your cluster is in by [contacting IBM Cloud support](https://cloud.ibm.com/docs/vlans?topic=vlans-ordering-premium-vlansordering-premium-vlans).
3. Note the new private and public VLAN IDs for each zone.
4. Note the name of your worker pools.

ibmcloud ks worker-pool ls --cluster <cluster_name_or_ID>
5. Use the zone network-set[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_zone_network_set) to change the worker pool network metadata.

ibmcloud ks zone network-set --zone <zone> --cluster <cluster_name_or_ID> -- worker-pool ls <worker-pool> --private-vlan <private_vlan_ID> --public-vlan <public_vlan_ID>
6. Multizone cluster only: Repeat Step 5 for each zone in your cluster.
7. Rebalance or resize your worker pool to add worker nodes that use the new VLAN IDs. For example:

ibmcloud ks worker-pool resize --cluster <cluster_name_or_ID> --worker-pool <worker_pool> --size-per-zone <number_of_workers_per_zone>
8. Verify that your worker nodes are created.

ibmcloud ks worker ls --cluster <cluster_name_or_ID> --worker-pool <worker_pool>
For each cluster that you want to use, log in to the cluster and create a secret named razee-git in the razeedeploy namespace by applying the following YAML file:

apiVersion: v1
data:
token: [BASE64_ENCODED_TOKEN_FROM_GITHUB_OR_GITLAB]
kind: Secret
metadata:
name: razee-git
namespace: razeedeploy
type: Opaque

You can have only one secret between GitHub and GitLab repositories.







 Creating Satellite configurations from the console 

To deploy an example app, see [Deploying Kubernetes resources to clusters with Satellite Config](https://cloud.ibm.com/docs/satellite?topic=satellite-begin-sat-config-tutorial).

To create your custom configuration, use the Satellite UI and follow these steps.



1. Log in to the [Satellite Config UI](https://cloud.ibm.com/satellite/configuration) with your IBM Cloud credentials.
2. Click Create configuration.
3. On the Browse templates page, select the GitOps template.
4. On the Configuration page, specify your configuration name and provider.



Configuration screen fields

 Field Description 

 Configuration name Enter the name of the Satellite configuration. 
 Provider Select the remote provider for the Satellite configurations, which stores the definitions of Kubernetes resources to be deployed to your clusters. Options are GitHub and GitLab. 



5. On the Subscription page, specify your repository URL, repository visibility, Git ref details, path to your file or directory, and cluster group to deploy to.



Subscription screen fields

 Field Description 

 Repository URL Enter the remote repository to use for this Satellite subscription. 
 Repository visibility Select whether this repository is public or private. 
 Git ref type Select the type of Git ref to use for this Satellite subscription. Valid values are Branch, Tag, Commit, and Release. 
 Branch/Tag/Commit/Release name Enter the Git ref to use for this Satellite subscription.
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
"activation_date": "2027-04-18",
"expiration_date": "2028-06-29",
"tags": [
{
"name": "first-tag",
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
"updated_at": "2022-03-09T11:26:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"referenced_keystores": [],
"instances": [
{
"id": "ea7b6b27-d71b-4fe9-bbfe-309c7ca713a6",
"label_in_keystore": "IBM CLOUD KEY",
"type": "secret_key",
"keystore": {
"group": "Production",
"type": "ibm_cloud_kms"
}
}
],
ibmcloud plugin list | grep schematics

Example output for blueprints support:

schematics 1.12.9 true
5. Show the Schematics plug-in.

ibmcloud plugin show schematics

Example output:

Plugin Name schematics[sch]
Plugin Version 1.12.9
Plugin SDK Version 0.8.0
Minimal IBM Cloud CLI version required 0.15.1
Private endpoints supported true

Commands:
schematics,sch Automate the deployment and management of IBM Cloud resources using Infrastructure as Code
schematics,sch workspace,ws Create and manage workspaces. Workspaces let you define the source control repository that contains your Terraform configuration and pass workspace-specific variables.
schematics,sch action,ac Create and manage Schematics actions. Action let you define the source control repository that contains your playbook yamls etc. and pass environment-specific variables.
schematics,sch job,j Create and manage Schematics jobs. Job let you manage all the jobs like creating/deleting/updating/retrieving.
schematics,sch plan Create a plan for an workspace. Plans show how resources would change if you applied the latest version of your workspace configuration.
schematics,sch apply Apply a plan to an workspace to deploy the latest version of your configuration.
schematics,sch refresh Refresh the workspace with latest version of your workspace configuration.
schematics,sch destroy Destroy resources in an existing workspace. This action cannot be reversed.
schematics,sch output Get all the output values from your workspace; (ex. result of terraform output command
schematics,sch version Report version information about the IBM Cloud Schematics CLI.
schematics,sch logs Show details about actions that ran against an workspace.
schematics,sch state Advanced state management
schematics,sch kms listing and enabling IBM Cloud Schematics kms instances and root keys .
},
"template": {
"id": "93777bca-baef-4070-b9b5-a2e6079df1b4",
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE"
},
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
"activation_date": "2027-04-18",
"expiration_date": "2028-06-29",
"tags": [
{
"name": "first-tag",
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
"updated_at": "2022-03-09T11:26:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"referenced_keystores": [],
"instances": [
{
"id": "ea7b6b27-d71b-4fe9-bbfe-309c7ca713a6",
"label_in_keystore": "IBM CLOUD KEY",
"type": "secret_key",
"keystore": {
"group": "Production",
"type": "ibm_cloud_kms"
}
}
],
"description": "IBM CLOUD key template description",
"label": "IBM CLOUD KEY",
"state": "active",
"size": "256",
"algorithm": "aes",
"verification_patterns": [
{
"method": "enc-zero",
"value": "DDFA4A"
}
],
"activation_date": "2027-04-18",
"expiration_date": "2028-06-29",
"tags": [
{
"name": "first-tag",
"value": "for-ibm"
}
],
"created_at": "2022-03-09T11:26:01Z",
"updated_at": "2022-03-09T11:26:04Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"referenced_keystores": [],
"instances": [
{
"id": "ea7b6b27-d71b-4fe9-bbfe-309c7ca713a6",
"label_in_keystore": "IBM CLOUD KEY",
"type": "secret_key",
"keystore": {
"group": "Production",
"type": "ibm_cloud_kms"
}
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/managed_keys/3dab42dc-6941-4841-8d27-4dabcc5aa09e"
}







 hpcs uko associated-resources-for-managed-key 

Obtain a list of resources associated with a managed key in IBM Cloud. These cloud resources are protected by the key that you specify.
* [ibmcloud schematics blueprint apply](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-apply)
* [ibmcloud schematics blueprint update](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-update)
* [ibmcloud schematics blueprint get](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-get)
* [ibmcloud schematics blueprint list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-list)
* [ibmcloud schematics blueprint destroy](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-destroy)
* [ibmcloud schematics blueprint delete](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-delete)
* [ibmcloud schematics blueprint job get](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-job-get)
* [ibmcloud schematics blueprint job list](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-job-list)
* [ibmcloud schematics blueprint job logs](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-blueprint-job-logs)
For Schematics Blueprints, the [Schematics plug-in](https://cloud.ibm.com/docs/schematics?topic=schematics-setup-cliinstall-schematics-plugin) version must be greater than the 1.12.5 version.

Refer to the section on [Creating Blueprints](https://cloud.ibm.com/docs/schematics?topic=schematics-create-blueprint-config&interface=cli) for examples of command syntax and output.

Syntax to create blueprint config using CLI parameters:

ibmcloud schematics blueprint create --name BLUEPRINT_NAME --resource-group RESOURCE_GROUP [--description BLUEPRINT_DESCRIPTION] --bp-git-url BLUEPRINT_GIT_URL -—bp-git-file BLUEPRINT_GIT_FILE [--bp-git-branch BLUEPRINT_GIT_BRANCH] [--bp-git-release BLUEPRINT_GIT_RELEASE] --input-git-url INPUT_GIT_URL -—input-git-file INPUT_GIT_FILE [--input-git-branch INPUT_GIT_BRANCH] [--input-git-release INPUT_GIT_RELEASE] [--inputs BLUEPRINT_INPUT_LIST] [-—input-file INPUT_FILE] [--github-token GITHUB_TOKEN] [--output OUTPUT]

Command options



Schematics blueprint create flags

 Flag Required / Optional Description 

 --name or -n Required Name of the blueprint. Delimited by double quotes if the name contains spaces. For example -name "my blueprint" 
 --resource-group or -r Required The management resource group for the blueprint. 
 description or --desc Optional The description of the blueprint. Delimited by double quotes if the description contains spaces. For example -description "my blueprint example" 
 --bp-git-url or --bu Required The blueprint Git URL. This is the URL of the repository containing the blueprint template.
ip_addresses = [module.ibm_vmware_solutions_shared_instance.default_external_network_ip]
}

service {
protocol = "tcp"
port = 22
}
}

resource "vcd_nsxv_dnat" "rule_internet_ssh" {
count = var.allow_ssh == true ? 1 :0

edge_gateway = module.ibm_vmware_solutions_shared_instance.edge_gateway_name
network_type = "ext"
network_name = module.ibm_vmware_solutions_shared_instance.default_gateway_network

original_address = module.ibm_vmware_solutions_shared_instance.default_external_network_ip
original_port = 22

translated_address = vcd_vapp_vm.vm_1.network[0].ip
translated_port = 22
protocol = "tcp"
}
Show more







 Step 3: Deploy using Schematics 

IBM Cloud Schematics delivers Terraform-as-a-Service so that you can use a high-level scripting language to model the resources that you want in your IBM Cloud environment, and enable Infrastructure as Code (IaC). You can organize your IBM Cloud resources across environments by using workspaces. Every workspace is connected to a GitHub repository that contains a set of Terraform configuration files, which build a Terraform template. Use Schematics to connect to the template hosted in GitHub which was reviewed above to configure networking and deploy a virtual machine.



 IBM Cloud Schematics 



1. Navigate to the [IBM Cloud Schematics](https://cloud.ibm.com/schematics/overview) overview page and click Create a workspace.
2. On the page, enter the link to our GitHub repository where our Terraform template for this tutorial is stored, https://github.com/IBM-Cloud/vmware-solutions-shared.
3. Select terraform_v1.1 as the Terraform version. Click Next.
4.
Follow the steps in [Deleting Schematics data](https://cloud.ibm.com/docs/schematics?topic=schematics-delete-schematics-data-intro&interface=ui) to destroy your workspace with Terraform.
2. See [Managing IBM Cloud resources](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycle) with Schematics to create, update, or delete the IBM Cloud resources.







 Next steps 



* Looking for additional workspace samples to work with? Check out the [sample workspaces](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-provider-templatesample). Check the Readme files of the examples for further customization and usage.
Then, run the [ibmcloud schematics refresh](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-refresh) and [ibmcloud schematics plan](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-plan) commands to verify the migrated Terraform version works properly.



Now you are at a current version of Terraform, and can continue by using the IBM Cloud Schematics Workspaces.
* [Upgrading the Terraform template version 1.x and above](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionterraform-version-upgrade1x)



* [Updating the Workspace Terraform 1.x version](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionterraform-version-upgrade1x-process)



* [Upgrading the Terraform template version 0.x to 1.x](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionterraform-version-upgrade0x)
* [Upgrading a Terraform v0.12 Workspace to v0.13](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionmigrate-steps12)
* [Upgrade Terraform template from v0.13 and higher to v1.0](https://cloud.ibm.com/docs/schematics?topic=schematics-migrating-terraform-versionupgrade-13-to10)



[Sample Terraform solutions](https://cloud.ibm.com/docs/schematics?topic=schematics-sol-overviewsol-overview)

[Compact config repo download](https://cloud.ibm.com/docs/schematics?topic=schematics-compact-downloadcompact-download)



* [Using compact download](https://cloud.ibm.com/docs/schematics?topic=schematics-compact-downloadcompact-active)
* [Note](https://cloud.ibm.com/docs/schematics?topic=schematics-compact-downloadcompact-note)



[Destroying workspace resources](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-destroy-wkssch-destroy-wks)
For more information, see [about taint and untaint command](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-taint) and see [Time out errors with IBM Cloud Schematics blog](https://www.ibm.com/cloud/blog/timeout-errors-with-ibm-cloud-schematics).

Documentation support to deploy resources in specific region or across multiple region
: For more information, see [Deploying IBM Cloud resources in a specific region or across multiple regions IBM Cloud resources](https://cloud.ibm.com/docs/schematics?topic=schematics-multi-region-deployment).

Documentation support to create workspace by using IBM Cloud Schematics resources
: For more information, see [Setting up Terraform for Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-terraform-setup).

One page view to create workspace by using UI, CLI, API, and Terraform switcher documentation
: For more information about IBM Cloud Schematics Workspaces, creation, see [Setting up workspaces](https://cloud.ibm.com/docs/schematics?topic=schematics-sch-create-wks&interface=ui).

Temporarily IBM Cloud Schematics Workspaces stop activity API is deactivated
: For more information, see [Stop an apply job](https://cloud.ibm.com/apidocs/schematics/schematicsdelete-workspace-activity) API.







 May 2021 

Review the release notes for May 2021.



 26 May 2021 

Version constraints support in IBM Cloud Schematics
: Specifying version constraints for Terraform and Ansible. For more information, see [specifying version constraints in Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-version-constraints).

Troubleshooting guide support
see [Managing IBM Cloud resources with Schematics](https://cloud.ibm.com/docs/schematics?topic=schematics-manage-lifecycle) to start creating, updating, or deleting IBM Cloud resources with Terraform.





 Verifying workspace update 

Verify that the workspace update is successfully as shown in the output.

Output

{
"id": "us-east.workspace.testwspace03jan.cf74cc48",
"name": "testwspace03jan",
"crn": "crn:v1:bluemix:public:schematics:us-south:a/1f7277194bb748cdb1d35fd8fb85a7cb:9ae7be42-0d59-415c-a6ce-0b662f520a4d:workspace:us-east.workspace.testwspace03jan.cf74cc48",
"type": [
"terraform_v1.0"
],
"description": "terraform workspace updated successfully",
"resource_group": "Default",
"location": "us-east",
"tags": [
"department:HR",
"application:compensation",
"environment:production"
],
"created_at": "2023-01-03T07:02:38.369965717Z",
"created_by": "test@in.ibm.com",
"status": "DRAFT",
"failure_reason": "",
"workspace_status_msg": {
"status_code": "200",
"status_msg": ""
},
"workspace_status": {
"frozen": true,
"frozen_by": "test@in.ibm.com",
"frozen_at": "2023-01-05T13:44:32.400019282Z",
* [Blueprint template YAML file](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-yaml-file)
* [Template inputs](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-input-statements)
* [Template outputs](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-output)
* [Module definitions](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-module)



* [Input files](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-input-file)
* [Dynamic inputs](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesblueprint-dynamic-input)
* [What's next?](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-templatesbp-def-whatsnext)



[Using Terraform modules with blueprint templates](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-terraformblueprint-terraform)



* [Root modules and Terraform configurations](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-terraformblueprint-root-module-config)
* [Child and reusable shared modules](https://cloud.ibm.com/docs/schematics?topic=schematics-blueprint-terraformblueprint-reusable-module)
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --placement-group 1d2afa0f-b9f2-4d85-ae35-a08885269644 Create instance template to be placed in the wanted placement group.
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --total-volume-bandwidth 4000 Create instance template with specific total volumes bandwidth
* ibmcloud is instance-template-create my-template-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 mx2-2x16 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --metadata-service true Create instance template with metadata service enabled or disabled
"id": "5295ad47-2ce9-43c3-b9e7-e5a9482c362b",
"name": "Test Vault Name",
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/vaults/5295ad47-2ce9-43c3-b9e7-e5a9482c362b"
},
"id": "ada4293c-07ed-4903-b3ee-419bd1a05fde",
"version": 0,
"name": "IBM-CLOUD-EXAMPLE-TEMPLATE",
"key": {
"size": "256",
"algorithm": "aes",
"activation_date": "P5Y1M1W2D",
"expiration_date": "P1Y2M1W4D",
"state": "active"
},
"description": "IBM CLOUD key template description",
"created_at": "2022-03-09T15:40:52Z",
"updated_at": "2022-03-09T15:40:52Z",
"created_by": "IBMid-1308197YB4",
"updated_by": "IBMid-1308197YB4",
"keystores": [
{
"group": "Production",
"type": "ibm_cloud_kms"
}
],
"href": "https://uko.us-south.hs-crypto.cloud.ibm.com:9549/api/v4/templates/ada4293c-07ed-4903-b3ee-419bd1a05fde"
}







 hpcs uko key-template-update 

Update attributes of a key template.