-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
🐛 cascade provider connection errors (#2728)
When an auxiliary provider is detected, its connection errors currently don't propagate after the initial connect call. Example: You are connecting to AWS and request `asset{*}`. This will request fields form the `os` provider, including `cpes` and `vulnerabilityReport`. The first call to `cpes` will fail to connect (as it should) and the error will be reported. On the second call (when we request `vulnerabilityReport`) it will return the provider during `provider := r.providers[info.Provider]; provider != nil `. However, that provider now doesn't have a valid connection. This PR adds the connection errors as a stable field within the provider and also returns them on returning a cached provider. Fixes #2724 Signed-off-by: Dominik Richter <[email protected]>
- Loading branch information
Showing
1 changed file
with
20 additions
and
25 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters