Micah Henning

Thanks for your reply. I tried this configuration but it did not change the outcome. The admin interface still seems to hardcode resources to port 80.

Nope, what you see above is my configuration.

I tried both to the same effect. :-/ Is there some way I can be more helpful? Some other configuration I can share?

I completely agree. Looking at these other issues as well I think the people have spoken. I think that conciseness is key to readability and explicit repetition of fields is...

The `archive_file` artifacts are produced during the plan stage. You just need to pass the artifacts across the stages. For instance, for Gitlab CI: ```yaml image: name: hashicorp/terraform:1.1.9 entrypoint: -...

Also having this issue with Boundary terraform provider 1.0.12 in a gitlab runner (docker linux image terraform:1.2.1) on amd64. ``` Error: error reading wrappers from "recovery_kms_hcl": Error configuring kms: error...

@louisruch Yes, it worked with 1.0.5, which I just upgraded from.

I stepped back versions one at a time and here are my results. ``` Error 1: Error: error reading wrappers from "recovery_kms_hcl": Error configuring kms: error fetching kms plugin rpc...

@louisruch If it’s helpful, I’m using the latest terraform docker image and experience the errors there as well.

@louisruch That certainly solved the issue I was seeing! But now I'm seeing a new one: The KMS recovery plugin configuration doesn't seem to work. Someone else already opened an...