[Feedback]: Manage module indexes in GitOps way along with Terraform configuation files about azure-verified-modules HOT 3 CLOSED

Hi @lonegunmanb,

Happy to take this one into our internal syncs that we have already scheduled as we are not super clear on what is meant here.

For clarity the CSV is used mainly for the module indexes and tracking owners and the modules status, that are then the source of truth for our telemetry reporting and a few other pieces.

Thanks

from azure-verified-modules.

Reopening due to OOF

from azure-verified-modules.

Hi @lonegunmanb,

Happy to take this one into our internal syncs that we have already scheduled as we are not super clear on what is meant here.

For clarity the CSV is used mainly for the module indexes and tracking owners and the modules status, that are then the source of truth for our telemetry reporting and a few other pieces.

Thanks

Echoing what @jtracey93 has mentioned, the CSVs are meant to be the source of truth for static data that requires the approval of an AVM core team member. We have also just recently implemented a new feature that shows the latest/all available versions of each module.

As an example for resource modules, we are also planning to implement a feature that will show all interfaces available in each module. Therefore, we will keep the modules indexes as is while continuously adding new dynamic features to the website representation.

from azure-verified-modules.