[JENKINS-73610] Allow for null values in "ensureFIPS" methods #55
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See JENKINS-73610
Fix the
NullPointerException
by allowingnull
value for bothensureFIPSCompliantURIRequest
andensureFIPSCompliantRequest
.Testing done
Existing tests have been amended to include a test with a
null
parameter, except forAbstractOpenShiftBearerTokenCredentialFIPSTest
because a call togetToken
without anURL
makes no sense.I also improved the test coverage by adding a test for
ensureFIPSCompliantRequest
Submitter checklist
Link to relevant pull requests, esp. upstream and downstream changes