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.

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

private endpoint in data resource ibm_secrets_manager_secret is incorrect #4187

Closed
argeiger opened this issue Nov 18, 2022 · 1 comment
Closed

Comments

@argeiger
Copy link

argeiger commented Nov 18, 2022

Terraform CLI and Terraform IBM Provider Version

Terraform v1.2.9
on darwin_amd64
+ provider registry.terraform.io/ibm-cloud/ibm v1.48.0-beta0

Affected Resource(s)

https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/data-sources/secrets_manager_secret

  • ibm_secrets_manager_secret

Terraform Configuration Files

provider "ibm" {
  # Configuration options
  visibility = "private"
  region     = "ca-tor"
}

data "ibm_secrets_manager_secret" "secrets_manager_secret" {
    instance_id = "<INSTANCE ID>"
    secret_type = "arbitrary"
    secret_id = "<SECRET ID>"
}

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.

image

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

@github-actions github-actions bot added the service/Secrets Manager Issues related to Secrets Manager label Nov 18, 2022
@IdanAdar IdanAdar removed the service/Secrets Manager Issues related to Secrets Manager label Mar 20, 2023
@IdanAdar
Copy link
Collaborator

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants