Skip to content

feat: add parameter to specify bicepconfig.json file - #20149

Draft
stektron wants to merge 1 commit into
Azure:mainfrom
stektron:select-bicep-config-file
Draft

feat: add parameter to specify bicepconfig.json file#20149
stektron wants to merge 1 commit into
Azure:mainfrom
stektron:select-bicep-config-file

Conversation

@stektron

@stektron stektron commented Aug 4, 2026

Copy link
Copy Markdown

Description

Add an optional parameter to specify an bicepconfig.json file that will override the default config file and the normal file resolution process

  • add a new, optional '--config' parameter to specify a specific bicepconfig.json
  • update unit tests
  • add fallback logic

Example Usage

bicep lint main.bicep --config /foo-bar/override.json

Checklist

Microsoft Reviewers: Open in CodeFlow

- add a new '--config' parameter to specify the location of the bicepconfig.json for override
- update unit tests
- add fallback logic
@stektron stektron closed this Aug 4, 2026
@stektron

stektron commented Aug 4, 2026

Copy link
Copy Markdown
Author

@microsoft-github-policy-service agree

@stektron stektron reopened this Aug 4, 2026
@stektron

stektron commented Aug 4, 2026

Copy link
Copy Markdown
Author

This commit is a working example of using the new --config parameter to specify the bicepconfig.json file when using the bicep lint command.

If this approach is accepted, I can add support for the other cli params (build, restore, decompile, generate-params, jsonrpc, snapshot). Though I'm not sure if bicep publish can use this.

To give more info, I was attempting to add this to the super-linter repo, and specifying a custom config file location is a bit of a wrinke
super-linter/super-linter#8025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant