Blob Containers can read the full Storage Account URL
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 81
Description
**Is your feature request related to a problem? Please describe.**
When creating and referencing a container within an Azure Storage account it would be nice not to have to rely on string interpolation to reference said container.
This came to light when doing SQL Server vulnerability assessments which requires the container path. It works with something like:
`${storageAccountVulnerability.properties.primaryEndpoints.blob}${storageAccountContainerVulnerability.name}`
Would love to be able to reference this with a property off of `storageAccountContainerVulnerability` in this case.
**Describe the solution you'd like**
Reference something like
`storageAccountContainerVulnerability.properties.URL`
This value is available in the portal.
Contributor guide
Research direction
Start by tracing how Azure Storage account and blob container resources expose properties, using storageAccountContainerVulnerability and its properties as the entry point. Check how the existing primaryEndpoints.blob value is represented and identify the tests for resource properties. Done means the container exposes its full storage URL directly and coverage verifies the value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100