Azure / bicep-registry-modules

Bicep registry modules
MIT License
499 stars 347 forks source link

[AVM Module Issue]: SQL Server Database Geo Secondary replica bug with attaching to ElasticPool, SKU Name and Tier should be NULL instead of defaults #3581

Open Bash- opened 1 week ago

Bash- commented 1 week ago

Check for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/sql/server

(Optional) Module Version

No response

Description

SQL Server Database Geo Secondary replica bug with attaching to ElasticPool, SKU Name and Tier should be NULL instead of defaults.

What I am doing: create a secondary SQL Server with databases in createMode: 'Secondary' and secondaryType: 'Geo' based on another SQL server. I am copying multiple databases and would like to make them part of an ElasticPool.

Normally you would set this by providing skuTier: 'Standard' and skuName: 'ElasticPool' to the database properties and setting the elasticPoolId. However, in case of a database with createMode 'Secondary' and using an ElasticPool it seems that the skuTier and skuName should not be filled (as it will take this from the original database?)

However, when I leave skuTier and skuName from the configuration, this module template falls back to default values of skuTier GeneralPurpose and skuName GP_Gen5_2.

I do not know exactly how it works with the secondary taking over skuTier and skuName, but I now had to work around this issue, hope someone can get it further.

(Optional) Correlation Id

No response

microsoft-github-policy-service[bot] commented 1 week 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 1 week ago

@Bash-, 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!

peterbud commented 1 week ago

Hi @Bash- , thanks for raising the issue.

Can you share the relevant part of your bicep file to be able to reproduce the error?

Normally you would set this by providing skuTier: 'Standard' and skuName: 'ElasticPool' to the database properties and setting the elasticPoolId.

Are you sure there is an 'ElasticPool' SKU available? In which region? I run this to get the list of available SKUs, and I don't have such SKU:

az sql db list-editions -l westus2 -o table 

Maybe it depends on the given subscription?

microsoft-github-policy-service[bot] commented 4 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)!
microsoft-github-policy-service[bot] commented 6 hours ago

[!IMPORTANT] @Bash-, this issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[!TIP] To prevent further actions to take effect, one of the following conditions must be met:

  • The author must respond in a comment within 3 days of this comment.
  • The "Status: No Recent Activity :zzz:" label must be removed.
  • If applicable, the "Status: Long Term :hourglass_flowing_sand:" or the "Needs: Module Owner :mega:" label must be added.