Azure / Azure/bicep

Deployment: Don't allow parameter files that are only a property bag

Open
#7,086 0 comments 0 reactions 0 assignees View on GitHub
devdiv story: bicep deploy
Dominant language
Bicep
Stars
3.6k
Forks
830
Avg merge
1d 21m
Merged PRs (30d)
79

Description

See in src/Bicep.LangServer/Deploy/DeploymentParametersHelper.cs:

// We'll work around the above issue by first detecting the format of the file.
// If it's in the format descibed in the docs, we'll extract the parameters value and use that for actual deployment.

We should require the parameters file to be a full JSON file, not just the property bag portion.

Contributor guide

Open the contributing guide

Research direction

Start in src/Bicep.LangServer/Deploy/DeploymentParametersHelper.cs and read the format-detection path described in the issue. Confirm how property-bag input is handled, then make the behavior accept only a full JSON parameters file; done means property-bag-only input is no longer allowed.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, json
Domain
cloud
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
50/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.