boundary-reference-architecture icon indicating copy to clipboard operation
boundary-reference-architecture copied to clipboard

terraform plan failure using Azure deployment

Open yz4898 opened this issue 4 years ago • 4 comments

Getting the following error from terraform plan:

│ Error: no suitable auth method information found │ │ with module.boundary.provider["registry.terraform.io/hashicorp/boundary"], │ on boundary/main.tf line 10, in provider "boundary": │ 10: provider "boundary" { │

yz4898 avatar Jun 28 '21 20:06 yz4898

@ned1313 Any chance you could take a look at this?

malnick avatar Aug 09 '21 15:08 malnick

Sure thing 👍.

On Mon, Aug 9, 2021, 11:18 AM Jeff Malnick @.***> wrote:

@ned1313 https://github.com/ned1313 Any chance you could take a look at this?

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/hashicorp/boundary-reference-architecture/issues/45#issuecomment-895312587, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTIYZOE4YE5B3LTBUUFCXLT37WTVANCNFSM47OVHKEQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .

ned1313 avatar Aug 09 '21 15:08 ned1313

@yz4898 Can you provide any more information about the error you are getting? Did you first set up the Azure environment with the KMS keys stored in Key Vault? The recovery key in Key Vault is used for initial configuration of Boundary.

ned1313 avatar Aug 31 '21 20:08 ned1313

I have the same issue using the AWS deployment.

I find, it works if I first deploy the AWS module, then attempt the boundary module.

Looking at the source, my guess is something is wrong here

https://github.com/hashicorp/terraform-provider-boundary/blob/main/internal/provider/provider.go#L91

jasonneurohr-stake avatar Nov 30 '21 22:11 jasonneurohr-stake