microsoft / microsoft/azure-container-apps
Managed resource group does not include deployment tags.
Nobody has claimed this yet.
- Dominant language
- Bicep
- Stars
- 445
- Forks
- 54
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 3
Description
This issue is a: (mark with an x)
- bug report -> please search issues before submitting
- documentation issue or request
- regression (a behavior that used to work and stopped in a new release)
Issue description
A clear and concise description of the observed issue.
Steps to reproduce
- Deploy a CAE with a custom VNET via portal/GUI
- Specify tags on the deployment
Expected behavior [What you expected to happen.]
Newly ME_* resource group should include tags from the deployment
Actual behavior [What actually happened.]
ME_* resource group does not include tags from the deployment
Additional context
Happens via TF/ARM when specifying infrastructureResourceGroup / infrastructure_resource_group_name
Having tags included are important for reporting/billing for most organizations.
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 reproducing a CAE deployment with a custom VNET and deployment tags through the portal/GUI or the Terraform/ARM paths using infrastructureResourceGroup or infrastructure_resource_group_name. Compare the deployment tags with those on the resulting ME_* resource group; done means the managed resource group includes the deployment tags for these paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100