Closed BernieWhite closed 1 year ago
@BernieWhite I can take it if you're already not working on it.
However, I'm wondering if we should check for the API version and have the rule working with API versions prior and the new ones with different vaules. Or if we should have it to the Standard
no matter what, and instead recommend customers to update their API versions.
@BenjaminEngeset Sure.
In terms of implementation. We should check API version otherwise we will break existing pipelines.
The logic would be something like this:
Standard
.2023-02-01
use Standard
.2023-02-01
use Paid
.@BenjaminEngeset Sure.
In terms of implementation. We should check API version otherwise we will break existing pipelines.
The logic would be something like this:
- If API version is not set, assume
Standard
.- If API version is greater then or equal to
2023-02-01
useStandard
.- If API version is less then
2023-02-01
usePaid
.
Great, thanks!
Description of the issue
AKS SKU names have changed for what is represented in code.
Instead of setting
sku.tier
toPaid
, it should beStandard
.Module in use and version:
Additional context
Related to #2065