Open sebbegg opened 2 months ago
Hey @sebbegg, thanks for reporting and sorry you've hit this. The pulumi-databricks provider uses the terraform-databricks provider under the hood: https://github.com/databricks/terraform-provider-databricks
Looking at the issue you've reported, it seems quite likely to be an issue with the terraform provider which we've inherited - could I kindly ask you to try to reproduce this in terraform and report in the TF provider? I'm having some issues with our databricks account right now and can't get the example working.
Seems it's an upstream issue, just created: https://github.com/databricks/terraform-provider-databricks/issues/4039
Describe what happened
When creating a
File
with a+
in its destination name the+
is removed and replaced with a whitespace.We're using git-based versioning for our jars/wheels which then end up looking e.g. like
some-lib-1.2.3.dev1+gf4a65aec.jar
. Uploading these leads to the file on databricks having the+
replaced with a whitespace.The
File.path
output still contains the+
though, so the omission certainly doesn't seem intended.Uploading files containing a
+
seems to be a valid/supported thing - it's possible e.g. via the databricks UI, so it doesn't seem to be a limitation.Sample program
In the catalog UI this shows up as:
Log output
No response
Affected Resource(s)
pulumi_databricks.File
Output of
pulumi about
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).