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

Tracking: issues with failing import #2028

Closed
t0yv0 opened this issue May 24, 2024 · 4 comments
Closed

Tracking: issues with failing import #2028

t0yv0 opened this issue May 24, 2024 · 4 comments
Assignees
Labels
kind/task Work that's part of an ongoing epic resolution/fixed This issue was fixed

Comments

@t0yv0
Copy link
Member

t0yv0 commented May 24, 2024

Tracking issues around pulumi import in bridged providers.

Themes here: Import maps to a series of calls such as Read and Check that causes mismatch between TF and Pulumi expectations. There are several known themes of failure that may inform mitigation:

  1. In TF, resources are more lax in returning data through Read that might not pass validators; Pulumi can mitigate by deploying data correction strategies either at the bridge or individual provider/resource level

  2. When Pulumi invokes a language-specific code generator it has strict type safety expectations on the data that is fed into it. In practice the data is often not type-conformant (for example required fields, are missing data). Pulumi can mitigate by cleaning the data to be type conformant to err on the side of succeeding with the import.

This issue is intended to track specific instances in bridged providers before suggesting more solutions in this space.

Examples

Mitigations

@t0yv0 t0yv0 added the kind/task Work that's part of an ongoing epic label May 24, 2024
@zbuchheit
Copy link

zbuchheit commented Jul 12, 2024

I believe I am having this issue as well with a user that has an internal private bridged provider. I will provide details separately.

@VenelinMartinov
Copy link
Contributor

@zbuchheit I'd be interested to hear about the details here, thanks!

@t0yv0
Copy link
Member Author

t0yv0 commented Sep 27, 2024

Thanks @corymhall for making a good dent in these set of issues with bridge fixes. I think this was useful to mine for opportunities even if we didn't find the bigger wins that we hoped to find. Closing as there are no immediate plans to move this forward.

@t0yv0 t0yv0 closed this as completed Sep 27, 2024
@pulumi-bot
Copy link
Contributor

Cannot close issue:

  • does not have required labels: resolution/

Please fix these problems and try again.

@pulumi-bot pulumi-bot reopened this Sep 27, 2024
@t0yv0 t0yv0 added the resolution/fixed This issue was fixed label Sep 27, 2024
@t0yv0 t0yv0 closed this as completed Sep 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Work that's part of an ongoing epic resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

5 participants