microsoft / microsoft/vscode-azureresourcegroups
Discussion: Should we expand support for `Edit Tags` for resources under the top-level grouping
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 78
- Forks
- 55
- Avg merge
- 16h 49m
- Merged PRs (30d)
- 139
Description
In Container Apps, the Managed Environment resource is the top level node. For the managed environment node, the edit tags command shows up just fine; however, for its child resource, the Container App, it is missing.
Let's have a short discussion during triage about if/how we want to support edit tags on child nodes further down the chain.
See contextValuesToAdd here:
azureUtils.ts > createGroupConfigFromResource
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
Start by reading azureUtils.ts, specifically createGroupConfigFromResource and the contextValuesToAdd handling. Review how Edit Tags appears for the Managed Environment and Container App nodes, then use triage to decide whether child resources should support it and what the intended scope is.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, typescript
- Domain
- cloud, devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100