Support manually setting contentVersion
Open
revisit
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 79
Description
1. could be a CLI argument
1. could be a keyword in the source code
Contributor guide
Research direction
The issue proposes two possible ways to support manually setting contentVersion: a CLI argument or a keyword in source code. First clarify which interface is intended and where contentVersion is currently determined; done means the selected mechanism lets users set it reliably and is covered by the relevant project checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100