Allow the ability for use-recent-api-version linter rule duration to be configurable

[jtracey93]

Creating as per the discussion in #8013 (comment)

We should consider allowing the use-recent-api-version linter rule duration to be configurable as this may be different per consumer of the rule rather than a hardcoded value/duration

[slavizh]

Additionally I would prefer to be able to configure the rule in a way to always warn me when there is a new version no matter the period and no matter that the new version is preview. We want to keep our templates up to date and currently this rule does not fully work in certain situations for us.

[ugreg]

@StephenWeatherford since this is no in progress curious on when this may be released. Does this mean that since the Milestone it is assigned to is due by May 01, 2023, we will be able to take advantage of this configuration sometime in May 2023?

[StephenWeatherford]

@ugreg Yes. Working on it now.

[StephenWeatherford]

@slavizh Stan...

Additionally I would prefer to be able to configure the rule in a way to always warn me when there is a new version no matter the period and no matter that the new version is preview. We want to keep our templates up to date and currently this rule does not fully work in certain situations for us.

Could you provide more details? I'm adding a new max-allowed-age-in-days property to the use-recent-api-version rule. If you set it to zero, then only the most recent apiVersion is allowed. With the exception that an older non-preview version is preferred over a newer preview version (same as currently behaves). For example, the most recent versions of Microsoft.DataMigration/services are:

• microsoft.DataMigration/services@2021-06-30 (newest non-preview version)
• microsoft.DataMigration/services@2021-10-30-preview
• microsoft.DataMigration/services@2022-01-30-preview
• microsoft.DataMigration/services@2022-03-30-preview (newest version)

If you specify services@2022-03-30-preview:

param location string
resource storageaccount 'Microsoft.DataMigration/services@2022-03-30-preview' = {
  name: 'name'
  location: location
  kind: 'StorageV2'
  sku: {
    name: 'Premium_LRS'
  }
}

it gives this warning:

Use more recent API version for 'Microsoft.DataMigration/services'. '2022-03-30-preview' is 371 days old, should be no more than 0 days old, or the most recent. Acceptable versions: 2021-06-30

This behavior was taken from the ARMTTK.

Are you saying you'd like a configuration to turn off the preference of non-preview for preview, so that 2022-03-30-preview is accepted if it's the newest, even if there's an old non-preview version? Thx.

[slavizh]

@StephenWeatherford yes, exactly that. As every Azure team develops differently and sometimes preview is the only one available with specific feature or it is the latest, we prefer during our development to know that there is a newer version even if preview. We can decide on per RP bases if we should now update the version or not. When our end users deploy our solutions they basically have different bicepconfig file than the one we use in development so they do not see these warnings. We basically guarantee and support what we have developed works.

[StephenWeatherford]

@StephenWeatherford yes, exactly that. As every Azure team develops differently and sometimes preview is the only one available with specific feature or it is the latest, we prefer during our development to know that there is a newer version even if preview. We can decide on per RP bases if we should now update the version or not. When our end users deploy our solutions they basically have different bicepconfig file than the one we use in development so they do not see these warnings. We basically guarantee and support what we have developed works.

@slavizh Thanks. Added #10345