Support for a single bicepconfig file for building bicep files

[ugreg]

Is there some supported way to have a single bicepconfig.json that all bicep source code from located in different directories can reference. If not, this would be something useful to add! It can function in a similar fashion to how a package.json at the root of an npm repo is used to download dependencies used across JavaScript files.

As seen in this repo there are multiple redundant placements of the bicepconfig.json, in the orchestration directory for example. I believe when building bicep files, a bicepconfig.json must always be included in the same directory as the bicep source file, the bicepconfig.json can't be associated with the bicep source file from another path?

A work around for now could be to implement copy logic to copy a single bicepconfig.json file across different directories during build time.

C:.
├───hubPeeredSpoke
│   └───bicepconfig.json
├───mgDiagSettingsAll
│   └───bicepconfig.json
└───subPlacementAll
    └───bicepconfig.json

[StefanIvemo]

You can use a single bicepconfig.json, the config file does not have to be in the same folder as your bicep file. The configuration file closest to the Bicep file in the directory hierarchy is used. In your example you could place it under C:\bicepconfig.json.

[ugreg]

In that case @StefanIvemo is this a valid setup in order for all 7 of these .bicep files to use the same linter configuration during build?

C:.
├───.github
├───bicep.config
├───modules
│   ├───folder
│   │   ├───file1.bicep
│   │   └───file2.bicep
│   ├───folder
│   │   └───file3.bicep
│   └───file4.bicep
├───orchestration
│   ├───folder
│   │   └───file5.bicep
│   ├───file6.bicep
│   ├───folder
│   │   └───file7.bicep
│   ├───file8.bicep
│   └───folder
│       └───file9.bicep
└───tests

[brwilkinson]

@ugreg that should be a valid way to setup the bicepconfig.json for all child modules.