Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Doc Fix #2706

Merged
merged 2 commits into from
Jun 3, 2021
Merged

Doc Fix #2706

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e90b20b
#2704
kavya498 Jun 3, 2021
2fdc80a
DocUpdate: Add Timeout Blocks to vpc cluster
kavya498 Jun 3, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions website/docs/r/container_vpc_cluster.html.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,15 @@ resource "ibm_container_vpc_worker_pool" "cluster_pool" {
}
}
```

## Timeouts

ibm_container_vpc_cluster provides the following [Timeouts](https://www.terraform.io/docs/configuration/resources.html#timeouts) configuration options:

* `create` - (Default 90 minutes) Used for creating Cluster.
* `delete` - (Default 45 minutes) Used for deleting Cluster.
* `update` - (Default 60 minutes) Used for updating Cluster.

## Argument reference
Review the argument references that you can specify for your resource.

Expand Down
2 changes: 1 addition & 1 deletion website/docs/r/kms_key.html.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,7 +57,7 @@ resource "ibm_resource_instance" "hpcs"{

Step 2: Initialize your service instance manually

To manage your keys, you need to initialize your service instance first. Two options are provided for initializing a service instance. You can use the IBM Hyper Protect Crypto Services Management Utilities to initialize a service instance by using master key parts stored on smart cards. This provides the highest level of security. You can also use the IBM Cloud Trusted Key Entry (TKE) command-line interface (CLI) plug-in to initialize your service instance. For more details refer [here(https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started#initialize-crypto)]
To manage your keys, you need to initialize your service instance first. Two options are provided for initializing a service instance. You can use the IBM Hyper Protect Crypto Services Management Utilities to initialize a service instance by using master key parts stored on smart cards. This provides the highest level of security. You can also use the IBM Cloud Trusted Key Entry (TKE) command-line interface (CLI) plug-in to initialize your service instance. For more details refer [here](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-get-started#initialize-crypto)

Step 3: Manage your keys using `ibm_kms_key`

Expand Down