-
Notifications
You must be signed in to change notification settings - Fork 22
OPCR-6: Customer Managed Key support for pro and active active subscriptions #635
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.
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
Conversation
| the subscription. The creation_plan block can ONLY be used for provisioning new | ||
| subscriptions, the block will be ignored if you make any further changes or try importing the resource (e.g. `terraform import` ...). | ||
|
|
||
| ~> **Note:** The CMK (customer managed encryption key) fields require a specific flow which involves a multi step apply. Please refer to the relevant documents if using these fields. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any links to consider putting in here. Maybe for a later release?
| the subscription. The creation_plan block can ONLY be used for provisioning new | ||
| subscriptions, the block will be ignored if you make any further changes or try importing the resource (e.g. `terraform import` ...). | ||
|
|
||
| ~> **Note:** The CMK (customer managed encryption key) fields require a specific flow which involves a multi step apply. Please refer to the relevant documents if using these fields. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are there any links to consider putting in here. Maybe for a later release?
…now multiple within the account
OPCR-6: Customer Managed Key support for pro and active active subscriptions
Customer Managed Key (CMK) support for Pro and AA subscriptions. This is supported through a set of new fields, and will require two
terraform applyto go through, so the creation of the subscriptions only completes on theupdatestep. This is due to a circular dependency between the RedisCloud API and GCP which would be difficult to resolve otherwise.