Refactor mocking of credentials resolvers for user agent tests #3580
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.
This PR reverts the previously reverted PR and updates the functional tests to provide only one credential provider in a credential resolver.
Description:
In the reverted PR, we initially mocked the functional tests using
get_credentialsto return a list containing only one credential. This resulted in a list where the specified credential was included, butNonevalues were returned for other credential providers. While this worked as expected in local environments, it could cause issues when lower-precedence credential providers are available.To address this, the PR now mocks the
create_credential_resolverfunction instead, returning a list that contains only the intended credential provider.Tests:
I verified that the functional tests related to registering credential feature ids run successfully.