Remove redundant options logging in Azure storage providers #9807
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.
AzureBlobGrainStorageandAzureTableGrainStoragewere logging their entire options objects atInformationlevel during initialization. This is redundant withSiloOptionsLoggerand can cause issues with loggers that don't handle complex object serialization well.Changes
InformationtoDebugAzureBlobGrainStorage: name andContainerNameAzureTableGrainStorage: provider name andTableNameThis aligns with the pattern used by other storage providers (e.g., Redis, which also uses
Debuglevel and logs specific properties).Original prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.
Microsoft Reviewers: Open in CodeFlow