Skip to content
This repository has been archived by the owner on Aug 16, 2022. It is now read-only.

Change Default Error Handling Behavior #973

Closed
bbernays opened this issue May 31, 2022 · 0 comments · Fixed by #982
Closed

Change Default Error Handling Behavior #973

bbernays opened this issue May 31, 2022 · 0 comments · Fixed by #982
Assignees
Labels
enhancement New feature or request

Comments

@bbernays
Copy link
Contributor

If a resource is deleted between the time the root resolver finishes and any nested resolvers run all nested resolvers will fail. The nested resolver logic should be able to identify ResourceNotFound errors and ignore them by default.

The current behavior is that the table only ignores permission errors and each API call has to check and handle different error codes

@roneli roneli self-assigned this Jun 1, 2022
@roneli roneli added the enhancement New feature or request label Jun 1, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants