Bicep snapshot additional parameter support
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 21m
- Merged PRs (30d)
- 79
Description
**Is your feature request related to a problem? Please describe.**
I have been having a play with the new bicep snapshot feature and really like the capability. I'm looking at how we may implement it's use but have found that it only runs with values in a/from .bicepparam file. We still have quite a few cases where we use .json parameters and we sometime use inline parameters too meaning that without the support for both inline and .json parameters our adoption will be slower
**Describe the solution you'd like**
When using the bicep snapshot command there is the option to use .bicepparam, .json and key=value parameters, like what is available when using deployment commands.
Contributor guide
Research direction
Start with the Bicep snapshot command and compare its parameter handling with deployment commands, focusing on the existing .bicepparam path. Done means snapshot accepts .bicepparam, .json, and inline key=value parameters as described; the issue does not name specific files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100