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
Populate inputs from live state for imports #1846
Conversation
Does the PR have any schema changes?Looking good! No breaking changes found. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks reasonable. To confirm my understanding, this would only apply to the import case because of the noOldInputs
check, right?
Yes - correct. |
31d1f41
to
51b32fa
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
1 similar comment
Does the PR have any schema changes?Looking good! No breaking changes found. |
Co-authored-by: Levi Blackstone <levi@pulumi.com>
51b32fa
to
5716a5e
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
5716a5e
to
b74ef30
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
1 similar comment
Does the PR have any schema changes?Looking good! No breaking changes found. |
e7f0662
to
a1b1898
Compare
Does the PR have any schema changes?Looking good! No breaking changes found. |
Does the PR have any schema changes?Looking good! No breaking changes found. |
Proposed changes
This change proposes an approach where we do a best-effort attempt at populating inputs from the live state for imports. Even though we tag input properties in the schema, we often have nested input fields mixed-in with dynamically populated fields so I am not entirely convinced this is the right approach. Curious to hear thoughts here.
Related issues (optional)
Fixes #1410.