https://pulumi.com
Join Slack
This message was deleted.
# general
s
This message was deleted.
g
also the fastly provider on the terraform side is so poorly done, I dont’ even want to get into it
b
Hey Thomas. Firstly, let me apologise for the poor experience here. As you note, sometimes we're privy to the issues with upstream providers and this is as a result of the bridging mechanism. It's rare there a bugs purely in the Pulumi bridge, and often the issues arise in the provider as you noted. As for your question about maintaining providers, the reason is primarily due to the engineering work it would take to manage and maintain so many provider forks. Our chosen path is to release and manage providers using API specs, as we are with the Azure, Google (beta) and AWS (in progress) providers. Obviously this doesn't help in this case With regards to your comment about updating the provider, we obviously want to get some of the new features in the tf provider, if you're running into issues I'd really recommend pinning your language SDKs to known good versions that work for you using 
package.json
| 
requirements.txt
| 
go.mod
g
Yeah we do use Pipenv with a Pipfile and lock to pin to 3.4.x.
I will say that the Fastly provider is terrible, even with Terraform so I can’t say this is a Pulumi specific problem.
🙂
I’m contemplating just discontinue using it it’s so bad, and just generating VCL myself.
(this specific provider)
@billowy-army-68599 unrelated to the upgrade, but I discovered that the Fastly Terraform provider doesn’t sanity check if you use the same backend “name” key… which bubbles up to the Pulumi bridge of course. 😂 So it means two same-named things in the Servicev1BackendArgs() Sequence [since it’s just a list of objects] will pollute each other as it reads and writes to the API. Brilliant… so I put a sanity check in my own implementation of the provider. 😄
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by