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.

Sign up for GitHub

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

Jump to bottom

Refresh shouldn't fail if resources aren't ready #3129

Open
blampe opened this issue Jul 24, 2024 · 0 comments
Open

Refresh shouldn't fail if resources aren't ready #3129

blampe opened this issue Jul 24, 2024 · 0 comments
Labels
kind/enhancement Improvements or new features

Comments

@blampe
Copy link
Contributor

blampe commented Jul 24, 2024 •
edited
Loading

v5 wishlist item. We might also consider this change for v4 as it arguably only "unbreaks" things.

We have an unusual code path around Read operations which fetch objects from the cluster but also evaluates those objects for readiness.

If the user refreshes an object which isn't ready, the operation will fail. This isn't really within the scope of a refresh operation, because there's nothing Pulumi could have done differently to make the operation succeed.

Instead, it would be appropriate from refresh operations to only update state and ignore readiness.

Related #605 #2824.
@blampe blampe added kind/enhancement Improvements or new features needs-triage Needs attention from the triage team and removed needs-triage Needs attention from the triage team labels Jul 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement Improvements or new features
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@blampe