Add test coverage for PRIVATE_KEY_JWT sink credential and 422 PRIVATE_KEY_JWT_NOT_CONFIGURED - #76
Merged
Merged
Conversation
…_KEY_JWT_NOT_CONFIGURED
albertoramosmonagas
marked this pull request as ready for review
September 1, 2026 15:34
CAMARA Validation — PASS (with warnings)0 errors, 2 warnings, 3 hints | Profile: standard |
Contributor
Author
|
Hi @eric-murray, ready for review. |
Contributor
Author
|
Hi @eric-murray, I plan to prepare the new release plan and the commonalities changes, any problem to merge this PR? |
eric-murray
approved these changes
Sep 24, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What type of PR is this?
Add one of the following kinds:
What this PR does / why we need it:
This PR adds the missing test coverage for PRIVATE_KEY_JWT sink credentials in the Predictive Connectivity Data API. It includes:
Which issue(s) this PR fixes:
Fixes #75
Special notes for reviewers:
The issue suggested either extending the existing 400.07 scenario outline or adding a dedicated scenario for PRIVATE_KEY_JWT. This PR follows the dedicated-scenario approach because PRIVATE_KEY_JWT is a supported credential type and therefore should not be included among the invalid credential examples. This keeps the test semantics aligned with the API schema and avoids asserting an incorrect 400 response.
Changelog input