Replace log analytics workspace which is GONE #49
Conversation
This file contains 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
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.
Delete entire Azure log analytics workspace that was the only place with traces of the HTTP web requests performed to the Azure storage blobs with the email SHA256.
Fixes https://github.com/moq/moq/issues/1395.
Verified by badge unavailable (which queries the old deleted workspace prior to this PR): https://img.shields.io/endpoint.svg?url=https://sponsorlink.devlooped.com/stats/projects&label=total%20projects&color=blue
The original workspace ID can be verified as deleted by someone on the Azure team, I suppose. It used to be
b5823173-1be6-4d23-92e6-4d2a4a89ad20if anyone from there can confirm externally.The way the blob storage requests made it into the analytics workspace was through a diagnostic settings in the storage account that forwarded storage events to the workspace. That was deleted prior to deleting the workspace:
As a side-effect, also, all previous HTTP requests with a hash that could have succeeded if the email hash belonged to a user actively sponsoring, will now return 404.