Closed ruaraikirkds closed 2 weeks ago
Thank you for reporting this @ruaraikirkds , I am sorry the error message is not informative. I'm going to keep this in the backlog for our team to pick up as capacity permits.
I cannot spot the issue at a glance, but in the meanwhile perhaps you can try getting a working starting example the might help avoid the error.
Unfortunately it looks like the Pulumi documentation page does not list examples for this resource at the moment: https://www.pulumi.com/registry/packages/databricks/api-docs/mwsvpcendpoint/
But there are some examples that could potentially be translated from the TF reference page: https://registry.terraform.io/providers/databricks/databricks/latest/docs/resources/mws_vpc_endpoint
There is also Pulumi AI that sometimes is a good source of example code.
Unfortunately, it looks like this issue hasn't seen any updates in a while. If you're still encountering this problem, could you leave a quick comment to let us know so we can prioritize it? (Commenting will bump it back into our triage queue.)
What happened?
Hello team!
I am running into an unexpected error when creating a Databricks VPC Endpoint using
MwsVpcEndpoint
from the @pulumi/databricks npm package as suggested in the reference docs.The error is quite vague so hoping for a little clarity as to whether this is a bug or an issue on my end. Please see below for simplified code for explanation.
Thanks!
Example
When running
pulumi up
, the following error is returned:The AWS resource is created and passes a valid id to
MwsVpcEndpoint
, and I have created a VPC endpoint in the Databricks UI with the AWS VPC endpoint id and it creates fine.For instance, when i manually created a VPC endpoint, then ran
pulumi up
I get the following:Output of
pulumi about
CLI
Version 3.93.0 Go Version go1.21.3 Go Compiler gc
Plugins NAME VERSION nodejs unknown
Host
OS darwin Version 14.3 Arch arm64
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).