-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The bridge does not accept secrets panic #2439
Comments
Facing similar issue with respect to deployment of my pulumi stack related to databricks. panic: fatal: An assertion has failed: The bridge does not accept secrets, so we should not encounter them here |
@MehulKothari-Circuitry, thanks for reporting. Which provider are you using? |
Fixed in #2438 |
Hey @VenelinMartinov the provider is Databricks |
Ok, thanks, I'll make a databricks release which should fix this! |
|
Ok, thanks, I'll make a databricks release which should fix this! |
…aform-bridge to v3.91.1 (#4526) This change includes a fix for a regression in handling secrets in the provider configuration properties (pulumi/pulumi-terraform-bridge#2439) that manifested as "the bridge does not accept secrets panic". This PR was generated via `$ upgrade-provider pulumi/pulumi-aws --kind=bridge --pr-reviewers=guineveresaenger`. --- - Upgrading pulumi-terraform-bridge from v3.91.0 to v3.91.1. - Upgrading pulumi-terraform-bridge/pf from v0.44.0 to v0.44.1.
Releasing AWS here: pulumi/pulumi-aws#4526 (review) apologies for the disruption again. |
Reopening until we resolve all provider issues |
GCP's was rolled into yesterday's upgrade. Released patches of all remaining providers affected:
|
I just pulled the latest versions and tried again, yet I still get the panic.
My dependencies are:
I did a fresh clean + install but still I get this error and from the logs it seems that old versions are still used, e.g. v3.133.0 for the pulumi sdk. Any advice on how to proceed? Best regards |
Do you know which provider is panic'ing Sascha, there should be some more context in the output compared to what you listed? We can double-check the release of that provider. |
Seems to me like something with OVH Provider is broken, but I am not sure. |
v3.91.0 contained a nasty bug: pulumi/pulumi-terraform-bridge#2439 (comment). Upgrading to v3.91.1 fixes the problem.
Hi @sdibernardo. pulumi-ovh is maintained by ovh, but I have opened a PR to fix the problem. Thanks for pointing this out. |
Thank you for taking action so quick 🥇 |
v3.91.0 contained a nasty bug: pulumi/pulumi-terraform-bridge#2439 (comment). Upgrading to v3.91.1 fixes the problem.
What happened?
After upgrading to the latest bridge, users encountered "The bridge does not accept secrets" panics.
Example
pulumi/pulumi-gcp#2405 is a good example where this was discovered.
Output of
pulumi about
N/A
Additional context
N/A
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).
The text was updated successfully, but these errors were encountered: