VS Code Bicep Extension marks module references to private registries as errors.

[Steviestevson]

Bicep version
VS Code Bicep Extension v0.32.4

Describe the bug
Ever since I use v032.4 all my module references to my private registry are shown as errors. The module references show as

The OCI artifact module alias name "redacted" does not exist in the built-in Bicep configuration.bicep[BCP213]

My module reference is looking like this:

module Redacted 'br/redacted:resourcegroup:0.2' = {
  name: redacted
  scope: subscription(redacted)
  params: {
    paramResourceGroupName: redacted
    location: location
    tags: tags
  }
}

To Reproduce
Steps to reproduce the behavior: Update the bicep extension to v0.32.4

Additional context
Downgrading the extension to v0.31.92 fixes the errors.

[jeskew]

Is the private registry something you authenticate to? Wondering if this may be related to #15403

[Steviestevson]

yes, the private registry I use is an azure container registry. I authenticate using Azure CLI and my user.

[StephenWeatherford]

#15403 shouldn't affect module restoration. I'm not seeing this issue in 0.32, at least not on Mac.

@Steviestevson it sounds like it's not finding the bicepconfig.json file. The error message should say "The OCI artifact module alias name "redacted" does not exist in the Bicep configuration "/user/path/bicepconfig.json" if it's finding the bicepconfig.json.

Where is the bicepconfig.json in relation to your bicep file? It should find it in any parent folder.

[Steviestevson]

Hey @StephenWeatherford !

sorry for late response. My bicepconfig.json is living in the same folder as my deplyoment and param files.

[Steviestevson]

@StephenWeatherford
There are updates:
My Windows device (bicep extension version: 0.32.4 AND 0.31.92) both show the same issue. It seems that bicep is unable to find my bicepconfig.json.

It does not matter where the bicepconfig file is saved. I also tried recreating the file from the VS Code dialogue.

When using literal paths to my modules, no error arise.

[Steviestevson]

@StephenWeatherford
Another update:

The error seems to be connected to the pathing (name of the repo). The name of the repo includes a 'space' (%20).

Might be related to #11469?

When I move the files to a path without a 'space' - everything works fine

[StephenWeatherford]

@Steviestevson Great observation. Adding @shenglol who was doing some engineering work around our use of file path URIs. Otherwise I can take a look week after next.