Azure / Azure/Microsoft-Defender-for-Cloud
Debug issue with Lab Module 19 - Defender for Storage - MoveMaliciousBlobEventTrigger.cs
- Dominant language
- PowerShell
- Stars
- 1.9k
- Forks
- 871
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 1
Description
**Describe the bug**
Hello team,
Referencing [lab module 19-Defender for storage](https://github.com/Azure/Microsoft-Defender-for-Cloud/blob/main/Labs/Modules/Module%2019%20-%20Defender%20for%20Storage.md), I've been trying to debug the code which can be used to quarantine blob using function app (https://github.com/Azure/Microsoft-Defender-for-Cloud/blob/main/Workflow%20automation/Move%20Malicious%20Blob%20FunctionApp%20Defender%20for%20Storage/MoveMaliciousBlobEventTrigger.cs) but when I debug the code I was not able to clear this one last error on missing namespace 'ETag' and couldn't seems to find the right package for it. Any advice is much appreciated.
Restore complete (1.6s)
Lab failed with 2 error(s) (11.4s)
C:\Users\alisapakpreo\Documents\Lab\MoveMaliciousBlob.cs(84,71): error CS0246: The type or namespace name 'ETag' could not be found (are you missing a using directive or an assembly reference?)
C:\Users\alisapakpreo\Documents\Lab\MoveMaliciousBlob.cs(116,67): error CS0246: The type or namespace name 'ETag' could not be found (are you missing a using directive or an assembly reference?)
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start with Workflow automation/Move Malicious Blob FunctionApp Defender for Storage/MoveMaliciousBlobEventTrigger.cs, focusing on the ETag references at lines 84 and 116 and the project's package references or using directives. Reproduce the failure with restore and build, then verify that both missing-namespace errors are resolved without introducing new build errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100