Skip to content

Commit

Permalink
chore(docs): Make plan explicit (#535)
Browse files Browse the repository at this point in the history
Keys created by this module will only be found by the UI or CLI if a Standard plan instance is ID is provided. Universal Key Orchestrator (UKO) plan instances will not be able to find/display keys.

Co-authored-by: Conall Ó Cofaigh <ocofaigh@ie.ibm.com>
  • Loading branch information
hancockp-at-ibm and ocofaigh authored Feb 13, 2024
1 parent 2c12613 commit cb3c5ef
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@
[![latest release](https://img.shields.io/github/v/release/terraform-ibm-modules/terraform-ibm-kms-key?logo=GitHub&sort=semver)](https://github.com/terraform-ibm-modules/terraform-ibm-kms-key/releases/latest)
[![Renovate enabled](https://img.shields.io/badge/renovate-enabled-brightgreen.svg)](https://renovatebot.com/)

This module supports creating a standard or root key in an existing key ring and KMS instance. KMS can be Key Protect or Hyper Protect Crypto Services(HPCS) instance. You can specify rotation and deletion policies for the keys.
This module supports creating a standard or root key in an existing key ring and KMS instance. KMS can be Key Protect or Hyper Protect Crypto Services (HPCS) Standard plan instance. You can specify rotation and deletion policies for the keys.

<!-- Below content is automatically populated via pre-commit hook -->
<!-- BEGIN OVERVIEW HOOK -->
Expand Down

0 comments on commit cb3c5ef

Please sign in to comment.