Modules that use experimental features should be marked as such in the bicep registry index

[alex-frankel]

Technically, nothing should prevent the CI from passing for a module with an experimental feature, but users should be aware when they are consuming a module that is experimental. Can this be marked that way in the registry and/or in vs code intellisense?

[shenglol]

I think we can check the language version in the generated ARM template. We can show the information in the Hover widget. The question is whether we should show it as an information level diagnostic as well. @alex-frankel @StephenWeatherford thoughts?

[ChrisSidebotham]

Dear @alex-frankel, Azure Verified Modules (AVM) will become the single Microsoft standard for Bicep modules. Transitioning to AVM, requests for new features or bug fixes will need to be submitted against the appropriate AVM module via AVM Module Issues.

As part of this transition, the new AVM CI environment is replacing the existing CI formerly leveraged within the Bicep Registry Modules (BRM) repository. As a result of this, issues and features related to the existing BRM CI will be closed. If you think your issue still needs addressing, please raise a new issue related to the AVM CI, here.

See this informational notice for more details on the upcoming changes.

Thank you for your understanding!