microsoft / microsoft/vscode-azureresourcegroups
log analytics resources
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
Referencing #1221 here - and apologies this may just pure ignorance on my part, but Log analytics workspaces are considered an 'azure' resource, but they don't seem to be listed as a resource that's available to interact with in this extension. Is this by design? As many things get folded into Visual Studio Code, I just see a lot of efficiency gains, at least for me, to be able to stay in vs code to do work. Are there plans to add mores types of resources to this extension? What about Log Analytics workspaces?
I think the original OP was asking for a new feature to be added to this extension to show those resource types, since Azure Data Studio appears to have that functionality and that is being retired in a week or two. In theory this would expose the available tables and in tandem, allow connections to those workspaces, so then folks could work against that stuff in vs code. This means things like IntelliSense will be aware of the tables, columns, etc. in these spaces and help developers/admins more quickly form queries. Many folks track these kinds of things in repos/shared spaces as well. Bonus points too if it could pull in available query packs and save queries as query packs. Understandably, additional extensions may be required to extend that functionality (similar to how Azure VMs and things have complimentary plugins).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing issue #1221 and how this extension currently exposes Azure resources, then clarify whether workspace browsing, table connections, IntelliSense, query packs, and saved queries are in scope. Done would require an agreed feature scope and implementation plan before coding.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100