[AVM Module Issue]: DiffBackupIntervalInHours Error when provisioning Hyperscale SQL server

avivansh commented 2 weeks ago

Check for previous/existing GitHub issues

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

Issue Type?

Bug

Module Name

avm/res/sql/server

(Optional) Module Version

0.4.0

Description

I am trying to deploy this module but facing this error

[{"code":"FeatureIsNotAvailableForServiceTier","message":"Updating property DiffBackupIntervalInHours is not available for Hyperscale service tier."}]}]}]}]}]}]}]}

module

param name string
param dbName string
param location string
param virtualNetwork string
param subnet string
param tags object = {}

module server 'br/public:avm/res/sql/server:0.4.0' = {
  name: 'serverDeployment'
  params: {
    // Required parameters
    name: name
    // Non-required parameters
    administrators: {
      azureADOnlyAuthentication: true
      login: '*******'
      principalType: 'Application'
      sid: '*****'
      tenantId: '******'
    }
    databases: [
      {
        backupLongTermRetentionPolicy: {
            monthlyRetention: 'PT0S'
        }
        backupShortTermRetentionPolicy: {
            retentionDays: 7
        }
        capacity: 0
        collation: 'SQL_Latin1_General_CP1_CI_AS'
        licenseType: 'LicenseIncluded'
        maxSizeBytes: 34359738368
        name: dbName
        skuName: 'HS_Gen5'
        skuTier: 'Hyperscale'
        skuCapacity: 4
      }
    ]
    location: location
    managedIdentities: {
      systemAssigned: true
    }
    restrictOutboundNetworkAccess: 'Disabled'
    securityAlertPolicies: [
      {
        emailAccountAdmins: true
        name: 'Default'
        state: 'Enabled'
      }
    ]
    tags: tags
    virtualNetworkRules: [
      {
        ignoreMissingVnetServiceEndpoint: true
        name: 'newVnetRule1'
        virtualNetworkSubnetId: resourceId('Microsoft.Network/virtualNetworks/subnets', virtualNetwork, subnet)
      }
    ]
  }
}

(Optional) Correlation Id

No response

microsoft-github-policy-service[bot] commented 2 weeks ago

[!IMPORTANT] The "Needs: Triage :mag:" 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[bot] commented 2 weeks ago

@avivansh, thanks for submitting this issue for the avm/res/sql/server module!

[!IMPORTANT] A member of the @Azure/avm-res-sql-server-module-owners-bicep or @Azure/avm-res-sql-server-module-contributors-bicep team will review it soon!

microsoft-github-policy-service[bot] commented 1 week ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.

To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!

microsoft-github-policy-service[bot] commented 5 days ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.

To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!