[AVM Module Issue]: app-configuration failed to deploy when sku changed from Developer to Standard

[OlehGap]

Check for previous/existing GitHub issues

• I have checked for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/app-configuration/configuration-store

(Optional) Module Version

0.9.2

Description

The module created app config with sku = 'Developer'.
When I wanted to upgrade to 'Standard' it fails with error

The property 'SoftDeleteRetentionInDays' is not valid. The soft delete retention period cannot be modified. (Code:InvalidProperty)

param sku string

module appConfig 'br/public:avm/res/app-configuration/configuration-store:0.9.2' = {
  name: '${deployment().name}-appconfig'
  scope: resourceGroup(subscriptionId, effectiveResourceGroupName!)
  dependsOn: [rg]
  params: {
    location: location
    name: 'riki-config-appcs-prod2'
    sku: sku
   softDeleteRetentionInDays: 7
  }
}

(Optional) Correlation Id

No response

[microsoft-github-policy-service]

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-organizer]

@OlehGap, thanks for submitting this issue for the avm/res/app-configuration/configuration-store module!

Important

A member of the @Azure/avm-res-appconfiguration-configurationstore-module-owners-bicep team will review it soon!

[microsoft-github-policy-service]

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 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

[AlexanderSehr]

Hola @JFolberth,
please triage this issue when you get the chance 🚀

[JFolberth]

This is an issue w/ the provider I believe.

I was able to recreate it via AVM deployment. Went ahead in the portal and upgraded to the Standard tier. Took the ARM template from that and deleted the AVM deployed resource.

Redeployed the AVM module in Developer tier then deployed the exported ARM template from the version that was upgraded to Standard and received the same error message. I also noticed when I upgraded the App Config it did not create a deployment under the Resource Group which leads me to believe the updating of SKU is occurring out side of an ARM template.

@AlexanderSehr are we able to engage the PG?