Allow applications to handle "not found" errors from `<resource>.get()`
### Problem Scenario It can be common to need to query for an existing resource and if it doesn't exist then take some other action. Currently Pulumi's `<resource>.get()` methods halt Pulumi execution without throwing an error that the user/application can catch and react to. ### Suggestion The results or error from `<resource>.get()` calls and data sources should be catchable so that users can take other actions as a result.
Posted by clstokes on Oct 17, 2019, 5:57 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
Allow applications to handle "not found" errors from `<resource>.get()`
### Problem Scenario It can be common to need to query for an existing resource and if it doesn't exist then take some other action. Currently Pulumi's `<resource>.get()` methods halt Pulumi execution without throwing an error that the user/application can catch and react to. ### Suggestion The results or error from `<resource>.get()` calls and data sources should be catchable so that users can take other actions as a result.
Comments (0)
No comments yet. Start the discussion.