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

Error: no suitable auth method information found #210

Open
rmgpinto opened this issue May 26, 2022 · 1 comment
Open

Error: no suitable auth method information found #210

rmgpinto opened this issue May 26, 2022 · 1 comment
Assignees
Labels

Comments

@rmgpinto
Copy link

I have the following provider declaration:

provider "boundary" {
  addr             = "https://${module.boundary.boundary_hostname}:9200"
  recovery_kms_hcl = <<-EOF
    kms "awskms" {
      purpose    = "recovery"
      key_id     = "global_root"
      access_key = "${module.boundary.boundary_iam.id}"
      secret_key = "${module.boundary.boundary_iam.secret}"
      kms_key_id = "${module.boundary.kms_recovery_key.id}"
    }
  EOF
}

This will only work, if module.boundary is applied beforehand.

addr and kms information is only known after module.boundary is applied. I'm not sure why isn't the provider deferring the evaluation of these variables until they are known.
Can the boundary provider attempt to contact boundary server during run time?

@william00179
Copy link

We are also seeing this problem. As boundary doesn't support the IAM role chaining that we require for our environment, we are trying to pass the variables in from an external script

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

No branches or pull requests

4 participants