Azure Verified Modules in Bicep not resolving modules list in intellisense[Question/Feedback]:

PhilipAnthonyMurray commented 2 months ago

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Description

I have started to look at Azure Verified Modules using Bicep in Visual Studio Code and I'm experiencing an issue getting Intellisense to resolve the modules list.

Creating a test.bicep file and referencing the br/public alias does not show me a list of published modules as I have seen in a couple of demos.

Full Error Message - The OCI artifact reference "br:mcr.microsoft.com/bicep/" after resolving alias "public" is not valid. The artifact path segment "bicep/" is not valid. Each artifact name path segment must be a lowercase alphanumeric string optionally separated by a ".", "_" , or "-".

Azure CLI Version - 2.60.0 Bicep Version - 0.26.170 Visual Studio Code Version - 1.88.1 Bicep Extension Version - 0.26.170

The issue happens on my work laptop on the corporate network but on my personal laptop\network it works as expected. Any idea why it cannot resolve the artifact reference, are there any firewall/proxy settings required for the endpoint?

It's also worth noting that if I manually complete the module reference it downloads it to the .bicep\br folder.

module nsg 'br/public:avm/res/network/network-security-group:0.1.3' = { }

shenglol commented 2 months ago

Hi @PhilipAnthonyMurray, could you verify if you can access https://aka.ms/br-module-index-data and https://live-data.bicep.azure.com/module-index from your corporate network?

PhilipAnthonyMurray commented 2 months ago

Hi @shenglol, yes I can access both in Chrome & Edge on the corp network.

PhilipAnthonyMurray commented 2 months ago

One more point, if I make a resource declaration, as below, intellisense works as expected.

resource aaa 'Microsoft.Web/sites/functions@2023-01-01' = { }

shenglol commented 1 month ago

One more point, if I make a resource declaration, as below, intellisense works as expected.

resource aaa 'Microsoft.Web/sites/functions@2023-01-01' = { }

IntelliSense for resource types in Bicep uses built-in type information within the Bicep compiler, so it works offline.

Hi @shenglol, yes I can access both in Chrome & Edge on the corp network.

This is odd, but I wonder if it's possible that the firewall is blocking requests from VS Code. To check this, you may try accessing the URLs using the REST Client VS Code extension, which you can find and install from here.

Additionally, could you please share the Bicep extension traces to further investigate the issue? Here’s how you can do it:

Access the Output panel, usually located at the bottom of the interface.
From the dropdown menu within the Output panel, choose 'Bicep'.
Look through the displayed information for any error messages that begin with Error retrieving MCR modules metadata.

If you come across any such errors, please copy and share them here so we can help troubleshoot the problem more effectively.