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.

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

storage backends should not fail if they cannot get single paths #22

Open
thomasmitchell opened this issue Nov 1, 2019 · 2 comments
Open

Comments

@thomasmitchell
Copy link
Collaborator

This may require a pre-check job to run to determine if the target cannot be reached or authenticated to at all. This way, we don't have to rely on the ability to get individual credentials to be the failure test.

@thomasmitchell
Copy link
Collaborator Author

The current behavior keeps all the certificates from being found if just one path returns an error. This is because I don't want failure to cause all the certificates for that backend to disappear from storage entirely. Keeping things around longer than they are there, potentially, causes false positives, which seems preferable to the opposite.

@thomasmitchell
Copy link
Collaborator Author

The middle ground here might be considering it a total failure if a List operation can't be done, but treating failures on individual Gets as warnings.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant