-
Notifications
You must be signed in to change notification settings - Fork 145
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
Raise exception when access is denied instead of silently failing #257
Conversation
I didn't see an existing issue except for the PR in #163, but we've run into this recently and it caused some serious issues and was VERY surprising to me as I just thought things were working, but it was actually silently failing. |
f0cca82
to
4d2ef3f
Compare
RETEST |
4d2ef3f
to
d7f66bb
Compare
Dear maintainers, this needs to be merged (unless you have a different change in place already) |
@jetersen I'm not sure if there are other maintainers here, but this PR has been open for nearly a year now. Any chance it could get a review/merge? We've been using it in our local fork with no issues in the last year. |
I have raised a Jenkins JIRA ticket to please merge this PR https://issues.jenkins.io/browse/JENKINS-72324 |
released in 362.v8dfe4061f29e |
This fixes #163 in the way asked for by @jetersen, but also adds a unit test to ensure correct behavior. I chose not to base it on the failIfNotFound flag since access denied shows a configuration issue that should be addressed immediately instead of "I have permissions, but it just doesn't exist" that failIfNotFound is for.