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

[convert] Ensure not supported lifecycle hook warning become an error #1803

Merged

Conversation

Zaid-Ajaj
Copy link
Contributor

Following up on pulumi/pulumi-converter-terraform#128 this PR turns warnings into errors when converting examples that have non-supported lifecycle hooks.

Addresses pulumi/pulumi-aws#3482

@Zaid-Ajaj Zaid-Ajaj requested a review from t0yv0 March 28, 2024 16:32
Copy link

codecov bot commented Mar 28, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.08%. Comparing base (3a2ed13) to head (1c48a51).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #1803      +/-   ##
==========================================
- Coverage   60.60%   60.08%   -0.52%     
==========================================
  Files         303      310       +7     
  Lines       42348    42731     +383     
==========================================
+ Hits        25667    25677      +10     
- Misses      15208    15581     +373     
  Partials     1473     1473              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Zaid-Ajaj Zaid-Ajaj requested a review from iwahbe March 28, 2024 21:28
@Zaid-Ajaj Zaid-Ajaj merged commit fb81f18 into master Mar 29, 2024
9 checks passed
@Zaid-Ajaj Zaid-Ajaj deleted the zaid/ensure-non-supported-lifecycle-hooks-error-out branch March 29, 2024 13:14
@t0yv0
Copy link
Member

t0yv0 commented Mar 29, 2024

Awesome, thank you!

Zaid-Ajaj added a commit that referenced this pull request Mar 29, 2024
#1811)

… before … (#1810)"

This reverts commit 67f7871 and gets
#1803 back in.

I originally reverted it since it was merged after the commit we
pre-tested the bridge upgrade on. Merging it back in
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