Open JoshuaXu-Wen opened 12 months ago
Bicep doesn't have any influence in how SQL MI manages other resources that it creates on your behalf. This will be a feature request to the SQL MI team and we would recommend opening a support case to get the ask triaged.
Ok, thanks Alex. Will report to the SQL MI team.
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub. Please see https://aka.ms/biceptypesinfo for troubleshooting help.
Bicep version Bicep CLI version 0.22.6
Describe the bug when creating a SQL Managed Instance with tags, a Virtual Cluster is created but no tag is added. And virtual cluster is a read-only resource, not able to change in the Bicep template. This will violate the Azure tag policy and cause a failure of resource deployment.
To Reproduce write a bicep template to create a SQL Managed Instance with tags verify the Virtual Cluster in the Azure portal, no tag is added
Additional context it would be better if Bicep could also allow to define the Virtual Cluster name when creating the SQL Managed Instance other than a system-generated name. From the link below, Virtual Cluster started to support tags in the latest API (2022-05) https://techcommunity.microsoft.com/t5/azure-sql-blog/virtual-clusters-hosting-azure-sql-managed-instance-are-enhanced/ba-p/3677437