-
Notifications
You must be signed in to change notification settings - Fork 43
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
Comments
I believe I am having this issue as well with a user that has an internal private bridged provider. I will provide details separately. |
@zbuchheit I'd be interested to hear about the details here, thanks! |
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. |
Cannot close issue:
Please fix these problems and try again. |
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:
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
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
validationMethod
from the code and don't show warning pulumi-aws#4054Mitigations
The text was updated successfully, but these errors were encountered: