Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[AVM Module Issue]: #3941

Open
1 task done
darrenFrowen opened this issue Dec 16, 2024 · 2 comments
Open
1 task done

[AVM Module Issue]: #3941

darrenFrowen opened this issue Dec 16, 2024 · 2 comments
Assignees
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue

Comments

@darrenFrowen
Copy link

Check for previous/existing GitHub issues

  • I have checked for previous/existing GitHub issues

Issue Type?

I'm not sure

Module Name

avm/res/compute/virtual-machine

(Optional) Module Version

Version > 0.8.0

Description

Hi, i previously deployed AVM modules version using 'br/public:avm/res/compute/virtual-machine:0.8.0'.

For this modules i am using a custom VM image located in galleryResourceId location.

param galleryResourceId         = '/subscriptions//resourceGroups/rg-we-com-h1s01-shared/providers/Microsoft.Compute/images/image_8.0.0'

// passed to VM module using the following
imageId: galleryResourceId

// Then referenced in the module template as follows. Note that the image has 1x OS disk and 8 Data Disks of vaious sizes

      osType: 'Linux'
      imageReference: {
        id: imageId
      }
      osDisk: {
        createOption: 'FromImage'
        managedDisk: {
          storageAccountType: 'Standard_LRS'
        }
        diskSizeGB: 20
      }
      dataDisks: [
        for (size, index) in dataDiskSizes: {
          lun: index + 1
        createOption: 'FromImage'
          managedDisk: {
            storageAccountType: 'Standard_LRS'
          }
          diskSizeGB: size
        }
      ]

When ran using v0.8.0 this works fine, if i try to move to a later version 0.10.1 (latest) or even 0.10.0 or 0.9.0 i encounter the following error.

Image

I use the bicepconfig.json to keep modules up to date hence linter showing later version available but i am unable to use. Is there something i am missing here.

{
    "analyzers": {
      "core": {
        "rules": {
          "use-recent-module-versions": {
            "level": "warning"
          }
        }
      }
    }
  }

(Optional) Correlation Id

No response

@darrenFrowen darrenFrowen added Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue labels Dec 16, 2024

Important

The "Needs: Triage 🔍" label must be removed once the triage process is complete!

Tip

For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

@avm-team-linter avm-team-linter bot added the Class: Resource Module 📦 This is a resource module label Dec 16, 2024
Copy link

@darrenFrowen, thanks for submitting this issue for the avm/res/compute/virtual-machine module!

Important

A member of the @Azure/avm-res-compute-virtualmachine-module-owners-bicep or @Azure/avm-res-compute-virtualmachine-module-contributors-bicep team will review it soon!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Class: Resource Module 📦 This is a resource module Needs: Triage 🔍 Maintainers need to triage still Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue
Projects
Status: Needs: Triage
Development

No branches or pull requests

2 participants