Update PersistenceManager not to fail when used in a read-only file system #3913
+65
−16
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.
Fixes #3801
Description
Updates the SDK's
PersistenceManager
not to fail when running on a read-only file system.I also included the suggested new option to ignore the legacy persistence store when the SDK is going through the default profile resolution search (via the
CredentialProfileStoreChain
).Motivation and Context
#3801 and
DOTNET-8123
Testing
DRY_RUN-5960c79f-a0e7-4dad-97c9-61374e1d2324
PersistenceManager
class directly and confirmed running it in a read-only file system does not throw a terminating error anymore:Before:
After:
Types of changes
License