Azure / Azure/bicep

Add "Insert Resource" to the Bicep.exe file, not just VS code extension

Open
#5,696 7 comments 0 reactions 0 assignees View on GitHub
enhancement good first issue
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.**
The "Insert Resource" command is *excellent* but only works in VS code as a function of the VS Code extension. Please add this to the bicep executable as

````
bicep.exe import "/subscription/.../object/ID"
````

**Describe the solution you'd like**
By adding this feature to the Bicep.exe file, scripting the output of many objects can be simplified.

````
bicep import "id1" >> outfile.bicep
bicep import "id2" >> outfile.bicep
bicep import "id3" >> outfile.bicep
bicep import "id4" >> outfile.bicep
````

`IMPORT` might be the wrong action word for the EXE. We have `build` and `Decompile`, maybe something more like `GET` or `READ`.

Contributor guide

Open the contributing guide

Research direction

Start by comparing the VS Code extension's existing "Insert Resource" command with the bicep.exe command surface, including the existing build and Decompile actions. Define the CLI action and its output behavior, then verify that repeated resource requests can produce usable Bicep suitable for scripting.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
cli, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.