Setting azure_native.dbforpostgresql.Configuration to a default value is ignored

[tpilewicz]

What happened?

When creating a azure_native.dbforpostgresql.Configuration with a value that happens to be the default, Pulumi does update the state with this value, but the update is ignored by Azure.

Example

For a postgres server with SKU Standard_D2ds_v5, with a max_connections configured at anything else than 859 (the default for this SKU), try to create a config set to 859:

new azure.dbforpostgresql.Configuration(
    `max-connections`,
    {
      configurationName: 'max_connections',
      resourceGroupName: config.resourceGroupName,
      serverName: postgresServer.name,
      source: 'user-override',
      value: '859',
    },
    {provider: config.azureProvider},
  )
}

The update will pass, but the setting won't be altered on the server, as can be seen with:

az postgres flexible-server parameter show \
    --resource-group xxx \
    --server-name xxx \
    --name max_connections \
    --query "{value:value, source:source, pendingRestart:isConfigPendingRestart}" -o json

Output of pulumi about

CLI
Version 3.245.0
Go Version go1.26.4
Go Compiler gc

Plugins
KIND NAME VERSION
language nodejs 3.245.0

Host
OS darwin
Version 26.5
Arch arm64

This project is written in nodejs: executable='/Users/pilewicz/.nvm/versions/node/v24.13.0/bin/node' version='v24.13.0' packagemanagerVersion='4.12.0' packagemanager='yarn'

Dependencies:
NAME VERSION
@pulumi/archive 0.3.3
@pulumi/aws 7.16.0
@pulumi/awsx 3.0.0
@pulumi/azure-native 3.12.1
@pulumi/command 1.1.0
@pulumi/eks 4.0.1
@pulumi/kubernetes 4.22.1
@pulumi/pulumi 3.112.0
@pulumi/random 4.18.2
@pulumi/synced-folder 0.11.1
@pulumi/tls 5.2.0

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).