Skip to content
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

Switch to failing tfgen by default on failed mapping errors #616

Merged
merged 1 commit into from Sep 28, 2022

Conversation

viveklak
Copy link
Contributor

@viveklak viveklak commented Sep 28, 2022

This will now require adding the environment variables to specific providers like alicloud that need this to opt-out but we should be erring for the common case instead of the previous behavior.

@viveklak viveklak requested a review from a team September 28, 2022 18:40
@github-actions
Copy link

Diff for pulumi-azuread with merge commit a73c81a

@github-actions
Copy link

Diff for pulumi-random with merge commit a73c81a

@github-actions
Copy link

Diff for pulumi-azure with merge commit a73c81a

@github-actions
Copy link

Diff for pulumi-aws with merge commit a73c81a

@viveklak
Copy link
Contributor Author

GCP failure should be fixed here: pulumi/pulumi-gcp#913

That is also proof of this working as expected.

@viveklak viveklak merged commit e27034b into master Sep 28, 2022
@viveklak viveklak deleted the vl/FlipMappingErrorPolarity branch September 28, 2022 19:13
@stack72
Copy link
Contributor

stack72 commented Sep 28, 2022

@viveklak i personally think this is a bad idea - there are a number of providers (like AliCloud) that will have issues here due to the upstream tf provider being broken as you noted

Adding this as the default means that 3rd party users themselves may have issues and they don't know how to opt-out

@viveklak
Copy link
Contributor Author

@viveklak i personally think this is a bad idea - there are a number of providers (like AliCloud) that will have issues here due to the upstream tf provider being broken as you noted

Adding this as the default means that 3rd party users themselves may have issues and they don't know how to opt-out

I am working on a change in ci-mgmt which will opt-in the behavior for these providers that don't comply with this. I understand there may be a long tail here but we need to find them one-way or the other anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants