-
Notifications
You must be signed in to change notification settings - Fork 681
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
ibm_kms_instance_policies fails when trying to communicate with a private only enabled Key Protect instance #5154
Comments
I am currently unable to reproduce the error.
My test setup:
If possible, could you link your tf code again? The link https://github.com/terraform-ibm-modules/terraform-ibm-base-security-services-da/pull/2 is broken(404). Edit: mistake in my setup, |
After updating to use allowed network flag, I am able to recreate the error
|
This description you provided accurately describes the problem
For now, the fastest fix is to add this flag endpoint_type to the instance policy resource. Will work on that. Thanks for reporting this bug |
…in fix for IBM-Cloud/terraform-provider-ibm#5154 <br>- `service_endpoints` now defaults to private for the DA solution (#453)
There seems to be a bug with the ibm_kms_instance_policies provider resource when it tries to run on a “private-only” Key Protect instance. The error returned is:
I am running in a Schematics environment on a VRF enabled account, so it should have access to the private endpoint. When I set the Key Protect instance to allow “public-and-private”, the error does not occur.
Other resources (such as ibm_kms_key) have an
endpoint_type
argument that can be set to public or private to allow you to choose which endpoint to use. But no such argument exists foribm_kms_instance_policies
so I’m wondering by any chance is the resource hard coded to use public endpoint, and hence failing here?Community Note
Terraform CLI and Terraform IBM Provider Version
tf 1.5.7
ibm provider 1.62.0
Affected Resource(s)
Terraform Configuration Files
The code is in root level of code in https://github.com/terraform-ibm-modules/terraform-ibm-base-security-services-da/pull/2
Debug Output
test.log.zip
Panic Output
Expected Behavior
No error
Actual Behavior
Steps to Reproduce
terraform apply
Important Factoids
(See description at top of this issue)
References
The text was updated successfully, but these errors were encountered: