[OperationalInsights] Workspaces eTag is invalid name, should be renamed -> etag
See original GitHub issue
az feedback
auto-generates most of the information requested below, as of CLI version 2.0.62
Related command
az monitor log-analytics workspace show --resource-group MyResourceGroup --workspace-name MyWorkspace
Describe the bug
Workspaces eTag is an invalid name, should be renamed -> etag
To Reproduce
Perform get workspace: az monitor log-analytics workspace show --resource-group MyResourceGroup --workspace-name MyWorkspace the response shouldn’t contain “eTag” property, but only “etag”
Expected behavior
CLI should return only “etag” and cancel out “eTag” property.
Environment summary
Additional context
Issue Analytics
- State:
- Created a year ago
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Setting up Log Analytics workspace for production in ...
The name for the Log Analytics workspace is unique across all of ... an eTag property should be added in the “savedSearches” resource...
Read more >AzSentinel.psm1 0.6.7
Enter the Workspace name ... With this function you can rename Azure Sentinel Alert rule ... ($rule | Select-Object lastModifiedUtc, etag, id, name),...
Read more >BlockBlobClient class
If a blob name includes ? or %, blob name must be encoded in the URL. BlockBlobClient(string ... This operation does not update...
Read more >microsoft/microsoft-graph-types
The maximum length of the company name is 64 chararcters. ... if the Outlook global address list should contain this user, otherwise false....
Read more >Turbot Releases | Help
The policy name is “AWS > VPC > Security Group Rules Approved Blacklisted ... Fixed: AWS > EC2 > Turbot Patching stack should...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks @kairu-ms
@dabenhamMic Thanks for reaching out to us and reporting this issue. We are looking into this issue and we will provide an update.
@sameergMS, @dadunl any update in past 2 months?