You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When visibility = "private", it tries to access private.resource-controller.cloud.ibm.com which does not exist unless you are in VPC infrastructure with a VPE. For this I executed within schematics.
Expected Behavior
resource controller is only in us-south and us-east for private and should have accessed its appropriate endpoint since we are not executing within VPC infrastructure.
I do not believe this is specific to the Secrets Manager data resource. Additionally, new data sources were shipped. I suggest to try with them just in case. If the issue continues, please re-open.
Terraform CLI and Terraform IBM Provider Version
Affected Resource(s)
https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/secrets_manager_secret
Terraform Configuration Files
Debug Output
When
visibility = "private"
, it tries to access private.resource-controller.cloud.ibm.com which does not exist unless you are in VPC infrastructure with a VPE. For this I executed within schematics.Expected Behavior
resource controller is only in us-south and us-east for private and should have accessed its appropriate endpoint since we are not executing within VPC infrastructure.
private.us-east.resource-controller.cloud.ibm.com
private.us-south.resource-controller.cloud.ibm.com
Actual Behavior
Goes to wrong endpoint for resource-controller
The text was updated successfully, but these errors were encountered: