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

[Epic] Q2 Bridge Quality #886

Closed
8 tasks done
t0yv0 opened this issue Mar 13, 2023 · 13 comments
Closed
8 tasks done

[Epic] Q2 Bridge Quality #886

t0yv0 opened this issue Mar 13, 2023 · 13 comments
Assignees
Labels
kind/epic Large new features or investments resolution/fixed This issue was fixed
Milestone

Comments

@t0yv0
Copy link
Member

t0yv0 commented Mar 13, 2023

Internal Design Doc

Timeline: Q2

To triage:

@t0yv0 t0yv0 added the kind/epic Large new features or investments label Mar 13, 2023
@t0yv0 t0yv0 self-assigned this Mar 13, 2023
@iwahbe
Copy link
Member

iwahbe commented Mar 17, 2023

For testing, should we add these?

@iwahbe
Copy link
Member

iwahbe commented Mar 17, 2023

We have agreed to address pulumi/pulumi-cloudflare#366 as part of bridge work in Q2. @t0yv0 can I add it to the epic.

This works in TF, so the problem is the bridge treating empty objects differently then TF.

@AaronFriel
Copy link
Contributor

Another candidate issue: pulumi/pulumi-random#286

@t0yv0 t0yv0 changed the title [Epic] Bridge Maintenance [Epic] Q2 Bridge Quality Apr 11, 2023
@t0yv0
Copy link
Member Author

t0yv0 commented Apr 13, 2023

I've missed #723 because I was scanning mostly bugs. I feel like it can fit here with #651 same area.

@iuliancristea
Copy link

Hi @t0yv0 - For #635, the issue is very much still there and causing problems.

@t0yv0
Copy link
Member Author

t0yv0 commented Apr 26, 2023

@phillipedwards
Copy link

@t0yv0 just curious, is there any timeline for #906? Would be a nice QOL improvement for helping users debug issues.

@t0yv0
Copy link
Member Author

t0yv0 commented May 10, 2023

That's a great idea! Yes, very valuable.

@t0yv0
Copy link
Member Author

t0yv0 commented May 12, 2023

#1118 came up as a real QOL improvement opportunity for the providers team; current workarounds include dropping fields entirely in providers such as azure-native to get past the limit on file size.

@AaronFriel
Copy link
Contributor

@t0yv0 should #540 be a candidate here as well? It looks like this affects multiple providers.

@t0yv0
Copy link
Member Author

t0yv0 commented May 30, 2023

Possibly pulumi/pulumi-aws#1655 - highly visible.

@t0yv0
Copy link
Member Author

t0yv0 commented Jul 7, 2023

The quarters are changing on us, closing this epic. We've made some progress here. I will open a new epic for Q3 once we have a chance to replan. AS always issue upvotes are highly appreciated as they inform priorities for maintainers.

@t0yv0 t0yv0 closed this as completed Jul 7, 2023
@pulumi-bot
Copy link
Contributor

Cannot close issue without required labels: resolution/

@pulumi-bot pulumi-bot reopened this Jul 7, 2023
@t0yv0 t0yv0 added the resolution/fixed This issue was fixed label Jul 7, 2023
@t0yv0 t0yv0 closed this as completed Jul 7, 2023
@lukehoban lukehoban modified the milestones: 0.89, 0.90 Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/epic Large new features or investments resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

8 participants