You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ziyeqf opened this issue
Feb 21, 2024
· 2 comments
Assignees
Labels
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue points to a problem in the management-plane of the library.
The vault is created with SystemAssigned, UserAssigned identity type.
Actual behavior
The vault is created with None Identity type.
Per test, it should be created with SystemAssigned identity type, then update to SystemAssgiend, UserAssigned.
Reproduction Steps
call the API
Environment
No response
The text was updated successfully, but these errors were encountered:
ziyeqf
added
the
bug
This issue requires a change to an existing behavior in the product in order to be resolved.
label
Feb 21, 2024
@ziyeqf this is known issue, type = "SystemAssigned, UserAssigned" with space in between is an invalid input.
Please try with "type": "SystemAssigned,UserAssigned".
zzhxiaofeng
added
the
Mgmt
This issue points to a problem in the management-plane of the library.
label
Feb 26, 2024
bugThis issue requires a change to an existing behavior in the product in order to be resolved.MgmtThis issue points to a problem in the management-plane of the library.
API Spec link
azure-rest-api-specs/specification/recoveryservices/resource-manager/Microsoft.RecoveryServices/stable/2022-10-01/vaults.json
Line 1737 in d420589
API Spec version
2022-10-01
Describe the bug
If create a vault (call the PUT method) with
SystemAssigned, UserAssigned
Identity type, the vault will be created withNone
Identity type.Request:
Response:
Expected behavior
The vault is created with
SystemAssigned, UserAssigned
identity type.Actual behavior
The vault is created with
None
Identity type.Per test, it should be created with
SystemAssigned
identity type, then update toSystemAssgiend, UserAssigned
.Reproduction Steps
call the API
Environment
No response
The text was updated successfully, but these errors were encountered: