Open yz4898 opened 3 years ago
@ned1313 Any chance you could take a look at this?
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 .
@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.
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
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" { │