[BUG] Azure.Provisioning.Sql exposes properties that are not available in the default api version

[sebastienros]

Library name and version

Azure.Provisioning.Sql 1.0.0

Describe the bug

Azure.Provisioning.Sql.SqlDatabase uses version "2021-11-01" by default, and doesn't expose "2023-08-01" (which is the latest stable?) in the list supported ones (c.f. ResourceVersions in the SqlDatabase class).

However, some properties like useFreeLimit or freeLimitExhaustionBehavior are only available with this version. Using them without setting the correct version manually will results in a warning during deployment.

When setting the API version manually the deployment works but the following message is returned:

Warning BCP081: Resource type "Microsoft.Sql/servers/databases@2023-08-01" does not have types available. Bicep is unable to validate resource properties prior to deployment, but this will not block the resource from being deployed. [https://aka.ms/bicep/core-diagnostics#BCP081]

Expected behavior

The newer api version should be used, or supported.

Actual behavior

Warning when using exposed properties without manually setting the resource version.

Reproduction Steps

var sqlDatabase = new SqlDatabase(bicepIdentifier, "2023-08-01")
{
    UseFreeLimit = true,
    FreeLimitExhaustionBehavior = FreeLimitExhaustionBehavior.AutoPause,
};

Environment

No response

[jsquire]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[ArcturusZhang]

:( this would be hard to resolve.
As a result of no breaking change policy for mgmt libraries, we must keep these properties that once released in one version forever, and the SDK currently do not have a mechanism of warning you about the versions of properties.
Currently the best we could do for this case, is that we hide those properties.