vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information, see [Registering NLB IPs with a DNS subdomain](https://cloud.ibm.com/docs/containers?topic=containers-loadbalancer_hostnameloadbalancer_hostname_dns).







 Version 0.2.99 

Version 0.2.99 of the CLI was released on 9 April 2019.



* Updates help text.
* Updates the Go version to 1.12.2.







 Version 0.2.95 

Version 0.2.95 of the CLI was released on 3 April 2019.



* Adds versioning support for managed cluster add-ons.
* Adds the [ibmcloud ks addon-versions](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_addon_versions) command.
* Adds the --version option to [ibmcloud ks cluster addon enable](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_addon_enable) commands.
* Updates the help text in various languages.
* Updates short links to documentation in help text.
* Fixes a bug where JSON error messages printed in an incorrect format.
* Fixes a bug where using the silent option (-s) on some commands prevented errors from printing.







 Version 0.2.80 

Version 0.2.80 of the CLI was released on 19 March 2019.



* Adds support for enabling [master-to-worker communication with service endpoints](https://cloud.ibm.com/docs/containers?topic=containers-plan_basicsworkeruser-master) in standard clusters in [VRF-enabled accounts](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf).
* Adds the --private-service-endpoint and --public-service-endpoint options to the [ibmcloud ks cluster-create](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_create) command.
* Adds the cluster ID to the output of ibmcloud ks cluster create.
* Updates the Go version to 1.12.10 to fix golang vulnerabilities for [CVE-2019-16276](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16276).







 Version 0.4.38 

Version 0.4.38 of the CLI was released on 14 October 2019.



* Adds the ibmcloud ks nlb-dns create vpc-classic, [ibmcloud ks nlb-dns replace](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_nlb-dns-replace), and ibmcloud ks nlb-dns rm vpc-classic commands to create and manage DNS subdomains for VPC load balancers in VPC clusters.
* Adds the --secret-namespace option to the ibmcloud ks nlb-dns create classic and ibmcloud ks nlb-dns create vpc-classic commands to specify the Kubernetes namespace that you want the SSL secret for the DNS subdomain to be created in.
* Updates status information of worker nodes for VPC clusters.
* Updates the help text in various languages.







 Version 0.4.31 

Version 0.4.31 of the CLI was released on 24 September 2019.



* Adds the --gateway-enabled option to the ibmcloud ks cluster create classic command to create a gateway-enabled cluster. You can enable a gateway only on standard, Kubernetes clusters during cluster creation.
* Removes the deprecated region get, region set, and region ls commands from help output.
* Updates command structure to the new spaced format in help output.
* Adds a warning to the output of legacy cluster config behavior. For more information, see the [version 1.0 plug-in documentation](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelogchangelog_beta).
Rolling back a deployment 

Sometimes, a new deployment to an environment behaves abnormally and requires a rollback to a last known good version. In such cases, you can use the continuous deployment pipeline to deploy a previous version of the inventory to the target environment (for example, stage or prod).

To roll back the deployment, complete these steps:



1. Select the version of the deployment (identified by commit-id) in the inventory to roll back to.
2. Revert the repository state to the identified commit.
3. Create a pull request to promote the reverted state.



The following commands show the scenario by using git commands:



1. List the commits and tags to identify the commit ID (version) to roll back to. For example, we identify refs/tags/8 to be the most recent good deployment.



 /c/usr/devsecops/compliance-inventory (master)
$ git show-ref --tags
09ce370c549a8313993ee143cbc9abc3127584c8 refs/tags/1
09ce370c549a8313993ee143cbc9abc3127584c8 refs/tags/2
09ce370c549a8313993ee143cbc9abc3127584c8 refs/tags/3
0cc6ddd7dafffdc5a955a640e678633c2710b174 refs/tags/4
0cc6ddd7dafffdc5a955a640e678633c2710b174 refs/tags/5
0cc6ddd7dafffdc5a955a640e678633c2710b174 refs/tags/6
83f7a87ee59185eaeac554bd3abeebfd2c1b4ad8 refs/tags/8
* kp import-token key-encrypt: encrypt the key that you want to import to the service
* kp import-token nonce-encrypt: encrypt the nonce that is generated by Key Protect
* kp import-token show: retrieve an import token
* kp key: perform operations on keys
* kp keys: list the keys that are available in your Key Protect instance
* kp region-set: target a different Key Protect regional endpoint







 Deprecate these commands 



* kp create: use kp import-token create or kp key create
* kp delete: use kp key delete
* kp get: use kp key show
* kp import-token encrypt-key: use kp import-token key-encrypt
* kp import-token encrypt-nonce: use kp import-token nonce-encrypt
* kp import-token get: use kp import-token show
* kp list: use kp keys
* kp policy: use kp key policies or kp key policy-update
* kp rotate: use kp key rotate
* kp unwrap: use kp key unwrap
* kp wrap: use kp key wrap







 Deprecated commands 

All deprecated commands work in versions 0.4.0 and 0.5.0. That is, version 0.5.0 is backwards compatible with versions 0.3.9 and 0.4.0. For example, you can issue the kp create command even though it's deprecated in version 0.5.0.

The intent is to remove support for deprecated commands in the next CLI version, which is anticipated the end of September, 2020.







 CLI version 0.3.9 (deprecated) 

Release date: 2019-11-11

Documentation: [CLI reference, version 0.3.9](https://cloud.ibm.com/docs/key-protect?topic=key-protect-cli-reference-039)



 Updates
acl deny [<hostname>]:[<port>]
no acl [<hostname>]:[<port>]
no acl

Note:no acl without any other parameters RESETS the ACL table and sets the access to DENY ALL.

You can find a sample ACL file [here](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-acl-files).

Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).





 Copying your ACL file into the Secure Gateway Docker client 

The Secure Gateway docker client essentially runs in it's own virtualization container. The filesystem of the hosting machine is therefore not directly accessible to processes that run inside the container, including the Secure Gateway client. Starting with version 1.8.0 of the Docker Engine, you can use the 'docker cp' command to import files that exist on your host into the container while it is running or stopped, this must be done in order to use the Secure Gateway client's ACL FILE interactive command.

To use the interactive 'cp' support in docker from your host to the docker instance you must be at docker 1.8.0. You can check this using docker --version

Once you have done this, your version should display as follows. It is recommended that you allow docker to run as non-root user, so run the command that is suggested after you have upgraded you engine to 1.8.0 or 1.8.2.

Client:
Version: 1.8.2
API version: 1.20
Go version: go1.4.2
Git commit: 0a8c2e3
Built: Thu Sep 10 19:21:21 UTC 2015
OS/Arch: linux/amd64

Server:
Version: 1.8.2
API version: 1.20
Go version: go1.4.2
Git commit: 0a8c2e3
* Fixes the error message for when no cluster name or ID is specified for ibmcloud oc worker get or ibmcloud oc worker-pool get.
* Adds public and private as supported values for the --hardware option of ibmcloud oc worker-pool create classic.
* When the --admin option is included in ibmcloud oc cluster config, removes -admin from the cluster name in the KUBECONFIG file path.
* Updates all command help to use the new space-separated syntax.







 Version 0.4.42 

Version 0.4.42 of the CLI was released on 24 October 2019.



* Adds the cluster ID to the output of ibmcloud oc cluster create.
* Updates the Go version to 1.12.10 to fix golang vulnerabilities for [CVE-2019-16276](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-16276).







 Version 0.4.38 

Version 0.4.38 of the CLI was released on 14 October 2019.



* Adds the --secret-namespace option to the ibmcloud oc nlb-dns create classic and ibmcloud oc nlb-dns create vpc-classic commands to specify the Kubernetes namespace that you want the SSL secret for the DNS subdomain to be created in.
* Updates status information of worker nodes for VPC clusters.
* Updates the help text in various languages.







 Version 0.4.31 

Version 0.4.31 of the CLI was released on 24 September 2019.



* Removes the deprecated region get, region set, and region ls commands from help output.
* Updates command structure to the new spaced format in help output.
* Adds a warning to the output of legacy cluster config behavior. For more information, see the [version 1.0 plug-in documentation](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_cli_changelogchangelog_beta).
To specify multiple worker pools, use multiple options, such as -p pool1 -p pool2. To remove the zone from all worker pools in the cluster, don't include this option.

-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 zone rm command 

ibmcloud ks zone rm --zone dal10 --cluster my_cluster









 ingress commands 

View and configure Ingress application load balancers (ALBs).

In CLI version 1.0.157 and later, the ibmcloud ks alb category is deprecated, and these commands are now listed in the ibmcloud ks ingress alb subcategory. For more information, see the [CLI change log](https://cloud.ibm.com/docs/containers?topic=containers-cs_cli_changelog10).



 ibmcloud ks ingress alb autoupdate disable 

Virtual Private Cloud

Classic infrastructure

Disable automatic updates of all Ingress ALB pods in a cluster.

By default, automatic updates to Ingress application load balancers (ALBs) are enabled. ALB pods are automatically updated when a new image version is available. To instead update the add-on manually, use this command to disable automatic updates. You can then update ALB pods by running the [ibmcloud ks ingress alb update command](https://cloud.ibm.com/docs/cli?topic=cli-kubernetes-service-clics_alb_update).

When you update the major or minor Kubernetes version of your cluster, IBM automatically makes necessary changes to the Ingress deployment, but does not change the image version of your Ingress ALB add-on. You are responsible for checking the compatibility of the latest Kubernetes versions and your Ingress ALB add-on images.

ibmcloud ks ingress alb autoupdate disable --cluster CLUSTER [-q]

Minimum required permissions
: Editor platform access role for the cluster in IBM Cloud Kubernetes Service
* When --output json is specified for the ibmcloud oc storage attachment get or ibmcloud oc storage attachment ls commands, fixes the output so that a volume table is not printed after the JSON output.
* Fixes a golang vulnerability for [CVE-2020-28852](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-28852).
* Updates the help text in various languages.







 Version 1.0.233 

Version 1.0.233 of the CLI was released on 1 March 2021.



* Adds satellite as a supported provider to the output of the ibmcloud oc cluster ls command.
* [Removes beta tags from ibmcloud sat commands for the generally available release of IBM Cloud Satellite.](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).







 Version 1.0.231 

Version 1.0.231 of the CLI was released on 25 February 2021.



* Updates the Go version to 1.15.8.
* Updates the help text in various languages.







 Version 1.0.223 

Version 1.0.223 of the CLI was released on 8 February 2021.



* Adds the [ibmcloud oc worker-pool label set](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_pool_label_set) and [ibmcloud oc worker-pool label rm](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_worker_pool_label_rm) commands to set and remove custom Kubernetes labels for all worker nodes in a worker pool.
* [Adds several commands and command changes for managing Red Hat OpenShift clusters in Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-satellite-cli-changelog).







 Version 1.0.208
"name": "gb", "type": [ "terraform_v0.13" ], "description": "migration workspace", "template_repo": { "url": "Provide your Git repository link" }, "workspace_status" : { "frozen": false }, "template_data": [{ "folder": ".", "type": "terraform_v0.13" }] } ```
12. Run these commands through command-line to create a new Terraform v0.13 workspace



* ibmcloud schematics workspace new --file workspace.json --state state.json.
* ibmcloud schematics workspace get --id <workspace-id> --json. If your workspace status is not inactive, wait for few seconds and retry the command.
* ibmcloud schematics plan id <workspace id>.
* ibmcloud schematics job get --id <job-id form plan> --json. If your workspace plan status is not success, wait for few seconds and retry the command.
* ibmcloud schematics apply --id <workspace id>.
* ibmcloud schematics job get --id <job-id from apply> --json.



13. [Optional] you can delete the Schematics workspace that uses Terraform v0.12.

Do not destroy the resources that are used by your old workspace.







 Upgrade Terraform template from v0.13 and higher to v1.0 

Versions 0.13 through 0.15 require a stepwise upgrade, 0.13 to 0.14, 0.14 to 0.15, 0.15 to 1.0.

The process is the same for each version step. It is mandatory that a Terraform Apply is run after each version change. This updates the Terraform state file with schema changes related to that version and that version only. After successfully upgrading a single version, the next version update can be performed.



1.
TotalCount: 2
Key Version ID Creation Date
14dfde20-a751-4c3e-b6b0-e8d00a17d8d1 2023-06-22T15:16:09Z
af61298c-d75d-42a8-aa76-e04178cf4685 2023-06-22T15:10:28Z

Note that if the -a flag is not given, the KEY_ACTION_INVALID_STATE_ERR is still returned for a key in a state other than active.







 Required parameters 



* KEY_ID_OR_ALIAS

The v4 UUID or alias of the root key that you used for the initial wrap request.
* -i, --instance-ID

The IBM Cloud instance ID that identifies your Key Protect instance.

You can set an environment variable instead of specifying -i with the following command: $ export KP_INSTANCE_ID=<INSTANCE_ID>.







 Optional parameters 



* --key-ring

A unique, human readable name for the key-ring. Required if the user doesn't have permissions on the default key ring.
* -n --number-of-key-versions

Restricts the number of key versions to be retrieved by the supplied integer value (default: 200).
* -o, --output

Set the CLI output format. By default, all commands print in table format. To change the output format to JSON, use --output json.
* -s --starting-offset

Retrievies the key versions from the offset as specified by the supplied integer value.
* -t --total-count

Used to reterieve total number of key versions for a key by the supplied integer value.
* -a --all-key-states

An optional flag to return the number of versions for all key states, including keys that are not active.









 kp key wrap
: This version of the CLI updates the buildrun submit command so that the --build option is no longer required. This update means that you can now use this single command to build a container image from a Git repository or local source without having to reference a build configuration.



* See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).
* See [Building a container image with stand-alone build commands (CLI)](https://cloud.ibm.com/docs/codeengine?topic=codeengine-build-standalone).







 02 June 2022 

CLI version 1.33.1 released
: See [CLI version history](https://cloud.ibm.com/docs/codeengine?topic=codeengine-cli_versions).

Updated available metrics for monitoring Code Engine
: No longer providing the following metrics:



* ibm_codeengine_application_request_duration_milliseconds_sum
* ibm_codeengine_application_request_duration_milliseconds_count
* ibm_codeengine_application_per_namespace_service_count



See [Monitoring for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-monitor).

Revised and improved topic organization of Code Engine limits and quotas
: See [Limits and quotas for Code Engine](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limits).







 May 2022 

Review the release notes for May 2022.



 26 May 2022 

CLI version 1.33.0 released
: This version of the CLI updates the build create command so that the --image and --registry-secret options are no longer required. This update means that you can choose to let Code Engine take care of building the image for you from your source and storing the image in IBM Cloud Container Registry with automatic access, or you can choose to specify registry details with a registry access secret for your build output.
Schematics introduces compact flag in the workspace create and update API
: You can now download the sub directory from the GIT repositories through Schematics. For more information, see [How can I download sub directory from the GIT repositories through Schematics?](https://cloud.ibm.com/docs/schematics?topic=schematics-workspaces-faqcompact-faq).

Importance of location and URL endpoint in workspace creation
: [Why do Schematics Workspaces create through API fails?](https://cloud.ibm.com/docs/schematics?topic=schematics-wks-create-api).







 August 2021 

Review the release notes for August 2021.



 27 August 2021 

Workspace update command enhancement
: The IBM Cloud Schematics supports pull request flag in the [Schematics Workspaces update](https://cloud.ibm.com/docs/schematics?topic=schematics-schematics-cli-referenceschematics-workspace-update) command.

Terraform v1.0 support
: IBM Cloud Schematics now supports Terraform v1.0 now. You can now select to run your infrastructure code with Terraform version 0.12 or 0.13 or 0.14, 0.15 or 1.0. Make sure that you use the syntax that is compatible with the Terraform version that you want to use. Note you can experience a unified console experience across all support platforms, and provides a provider based sensitivity and sensitive functions. For more information about Terraform v1.0 availability from HashiCorp Language, see [Terraform v1.0 general availability](https://developer.hashicorp.com/terraform/language/v1.1.x/upgrade-guides/1-0).

IBM Cloud Schematics support job queue logs enhancement
: For more information about viewing job queue logs, see [Reviewing the Schematics job details](https://cloud.ibm.com/docs/schematics?topic=schematics-interrupt-jobsch-job-logs).
* Adds the [ibmcloud ks credential get command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_credential_get).
* Adds support for the storage log source to all cluster logging commands. For more information, see [Understanding cluster and app log forwarding](https://cloud.ibm.com/docs/containers?topic=containers-healthlogging).
* Adds the --network option to the [ibmcloud ks cluster config command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_config), which downloads the Calico configuration file to run all Calico commands.
* Minor bug fixes and refactoring.







 Version 0.1.593 

Version 0.1.593 of the CLI was released on 10 October 2018.



* Adds the resource group ID to the output of ibmcloud ks cluster get.
* When [Key Protect is enabled](https://cloud.ibm.com/docs/containers?topic=containers-encryptionkeyprotect) as a key management service (KMS) provider in your cluster, adds the KMS enabled field in the output of ibmcloud ks cluster get.







 Version 0.1.591 

Version 0.1.591 of the CLI was released on 2 October 2018.



* Adds support for [resource groups](https://cloud.ibm.com/docs/containers?topic=containers-clusters&interface=ui).







 Version 0.1.590 

Version 0.1.590 of the CLI was released on 1 October 2018.



* Adds the [ibmcloud ks logging collect](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli) and [ibmcloud ks logging collect-status](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli) commands for collecting API server logs in your cluster.
1.8.1 17 April 2022 Fixes alias deprecation display message for the Schematics JSON output. 
 1.8.0 13 March 2022 Supports passing .tfvars and .json files to plan and apply command. Usage of ibmcloud terraform command displays warning message. The version also supports private Schematics endpoints through command-line, and enhances the tabular view output to list the provisioned resource in Schematics Workspace. 
 1.7.3 4 March 2022 Supports passing vars files to command-line plan command, displays commit ID in ibmcloud schematics workspace get command, and edited the ibmcloud schematics workspace state show command description. 
 1.7.2 17 February 2022 Supports Linux™ arm64 and Mac OS arm64 platform binaries. Fixes related to stdout/stderr stream, invalid TF vars file and translation are released. 
 1.7.1 11 February 2022 Support for trace logging and added integration tests for few commands. Fixes to update env values metadata, panic for invalid flags, and ibmcloud schematics workspace output command is disabled. 
 1.7.0 12 January 2022 Displays Terraform v11.0 deprecation message after command execution. Fix command-line alias. Remove the appearance of the duplicate strings. Support global time in the log file. 
 1.6.2 2 December 2021 Support for non-English translations. Fix apply command --var-file and actions --target not setting argument. Fix pipeline vulnerability. 
 1.6.1 21 October 2021 Supports winrm for Schematics Actions. Added the --inventory-connection-type, --bastion-credential-json and --credential-json option value to the create, and config updates. Updated non-english translations for the command-line. Fixed duplication display of command-object argument in ibmcloud schematics jobs run interactive mode. 
 1.6.0 29 September 2021 Support for linux-ppc64le, and linux-s390x binaries. Lists Terraform v1.0 in the details panel.
Commands to manage the agent 



 Get the agent version 

logdna-agent --version





 Enable the agent on boot 

sudo systemctl enable logdna-agent





 Check the status of the agent 

systemctl status logdna-agent





 Start the agent 

sudo systemctl start logdna-agent





 Stop the agent 

sudo systemctl stop logdna-agent





 Get a log trace from the agent 

journalctl _SYSTEMD_INVOCATION_ID=systemctl show -p InvocationID --value logdna-agent.service





 Delete the agent 

yum remove logdna-agent