Bicep snapshot additional features
- Dominant language
- Bicep
- Stars
- 3.6k
- Forks
- 830
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 79
Description
**Is your feature request related to a problem? Please describe.**
I am using the Bicep snapshot functionality more frequently (as I'm sure many others are) and it would be good to know of any of the following features are planned?
**Describe the solution you'd like**
- The option to create snapshots using the Visual Studio Code extension, ie: in right click menus on/in active file types which are supported, similar to how "**Build Parameters File**" & "**Build ARM Template**" work in the UI.
- The ability to use `--pattern` with `bicep snapshot` like the other bicep commands. eg: `bicep snapshot --pattern './dir/**/*.bicepparam'`, This would make it orders of magnitude faster than looping over multiple files and processing each using `bicep snapshot example.bicepparam`
I have built a custom binary using **Bicep.RpcClient** that uses a pattern to snapshot files as above, however it would be great if this was supported natively within the `bicep` binary.
Many Thanks
Contributor guide
Research direction
Start by reviewing the bicep snapshot command, the Visual Studio Code extension actions, and the Bicep.RpcClient usage described in the issue. Determine how native pattern handling and extension-triggered snapshots should fit the existing workflows. Done means both requested capabilities are supported consistently by the bicep binary and the VS Code extension.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, vscode
- Domain
- cli, cloud, developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100