Josh Kodroff

@joeypunzel Bridged (that is, non-native) providers in Pulumi take a Terraform provider as a dependency. We do not take a dependency on the Terraform core.

Verified that this is still an issue and also does not seem to occur with an equivalent TF template. Going to check into the Diff behavior in the bridge.

@pgavlin Any commented out stuff is from me and @stack72 attempting to debug, but it should be pretty close to the original: ```terraform terraform { required_providers { aws = {...

This sounds like something that should be an issue in the upstream provider, but I don't see any obvious corresponding issue: https://github.com/hashicorp/terraform-provider-azurerm/issues?q=is%3Aissue+key+vault+label%3Aservice%2Fkey-vault+label%3Abug+is%3Aclosed

@EdonGashi Could you add an example of `Program.cs` calling `Parser.Default` to your example above?

Seems like this issue should be closed due to the above PR?

@Frassle If we have the context to know we are in an apply, even throwing an exception with an actionable error message (don't do this - do it like this...

This issue also affects `aws.cloudtrail.Trail`, and so I'm suspicious that it may affect all MLCs. Note that using `providers` instead of `provider` seemingly has no effect: ```typescript import * as...

Verified that the same behavior exhibits in Python.

@RobbieMcKinstry No - if it's in the schema and not in the generated docs, it's not in the bridge, which is where I was focusing my efforts for examples conversion.