Resource property 'part-of-stack'
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure
- Domain
- infrastructure
Research direction
The issue names no files, tests, or entry points. Start by surveying the Deployment Stacks CLI scripts and Azure resource handling, then define how stack membership should be exposed for attached and detached resources and what behavior would demonstrate that the feature is complete.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
It would be great to see, for each Azure resource, if it is part of a stack.
Let's assume that over time many users will migrate to stacks for a strong grouping of resources, tracking ownership, and grouping resources for application (components). Now, many teams will likely use updateBehavior=detach as no one accidentally wants to remove something that is still (unknowingly) in use. This behavior would lead to many resources that are no longer part of any stack, most likely because they can be removed.
Having clear visibility into resources that are (no longer) part of a stack can be a great way for tracking no longer used resources.
- Dominant language
- Bicep
- Stars
- 101
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
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.
More from Azure/deployment-stacks
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
Azure/deployment-stacks#255 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 52/100
Azure/deployment-stacks#254 ·
-
Tag deletion call-outs create noise in stack what-if results; deployment stacks should cover tags Open
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Azure/deployment-stacks#253 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/deployment-stacks#252 · 2 comments ·
-
known limitation
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Azure/deployment-stacks#251 · 1 reaction ·
All issues in Azure/deployment-stacks
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
repo:raw-data
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
hotosm/raw-data-api#316 · 1 comment ·
-
agentic-workflows cascade-suspected
Difficulty 2/5 1-3 hours Newbie friendliness 68/100