-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] - Sku gotten from databases.get gives InvalidSku for databases.beginCreateOrUpdateAndWait #33101
Comments
Hi @michal-rak-cyera what's the region you use when you create this resource |
This happened with a number of regions, ex:
even though when using
The problem is the type of sku.name is different for the getter method and the setter method |
I try to list all the skus with eastus, here is the result
looks Standard doesn't exist in this list |
When you do |
@michal-rak-cyera
but this operation's final response body of sku became
which is consistent with the get() result.
from the this list, ServiceObjective should be the expected sku name not the Sku, This will make confusion for customers to set the sku. |
@michal-rak-cyera you can also create a service support ticket to get direct support from the service team. |
Describe the bug
databases.beginCreateOrUpdateAndWait()
withcreateMode: KnownCreateMode.Copy
andparameters: Database
, whereDatabase
hassku.name: 'Standard'
returns Rest ErrorInvalidSku. The sku 'Standard' specified is invalid.
, even though this is thesku.name
that is returned fromdatabases.get()
.This reproduces for other DTU sku-s where the Sku name is different from the corresponding
ServiceLevelObjective.name
, but not for vCore DTU-s.However, manual setting of
sku.name
to be the correspondingserviceLevelObjective.name
works, and does not return Rest ErrorTo Reproduce
Get an AzureSQL Database using
databases.get()
where it'sSku
isStandard
with capacity10
. Try sending the gottensku
attribute as a parameter indatabases.beginCreateOrUpdateAndWait()
when usingcreateMode: KnownCreateMode.Copy
(known, possibly in other create modes too)Expected behavior
Sku
interface that returns fromdatabases.get()
matches interface expected inparameters
fordatabases.beginCreateOrUpdateAndWait()
The text was updated successfully, but these errors were encountered: