Skip to content
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] [RecoveryServices@2022-10-01]: Create Vault with SystemAssigned, UserAssigned identity type not work #27851

Open
ziyeqf opened this issue Feb 21, 2024 · 2 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Mgmt This issue points to a problem in the management-plane of the library.

Comments

@ziyeqf
Copy link
Contributor

ziyeqf commented Feb 21, 2024

API Spec link

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 with None Identity type.

Request:

{
    "identity": {
        "type": "SystemAssigned, UserAssigned",
        "userAssignedIdentities": {
            "******"
        }
    },
    "location": "westus2",
    "properties": {
        "publicNetworkAccess": "Enabled"
    },
    "sku": {
        "name": "Standard"
    },
    "tags": {}
}

Response:

{
    "etag": "W/\"datetime'2024-02-21T07%3A14%3A49.4027418Z'\"",
    "id": "****",
    "identity": {
        "type": "None"
    },
    "location": "westus2",
    "name": "****",
    "properties": {
        "backupStorageVersion": "Unassigned",
        "privateEndpointStateForBackup": "None",
        "privateEndpointStateForSiteRecovery": "None",
        "provisioningState": "Succeeded",
        "publicNetworkAccess": "Enabled",
        "redundancySettings": {
            "crossRegionRestore": "Disabled",
            "standardTierStorageRedundancy": "GeoRedundant"
        }
    },
    "sku": {
        "name": "Standard"
    },
    "tags": {},
    "type": "Microsoft.RecoveryServices/vaults"
}

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 to SystemAssgiend, UserAssigned.

Reproduction Steps

call the API

Environment

No response

@ziyeqf 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
@zzhxiaofeng
Copy link
Member

@shesamian Please help have a look, thank you.

@umpatel
Copy link
Contributor

umpatel commented Feb 23, 2024

@ziyeqf this is known issue, type = "SystemAssigned, UserAssigned" with space in between is an invalid input.
Please try with "type": "SystemAssigned,UserAssigned".

@zzhxiaofeng zzhxiaofeng added the Mgmt This issue points to a problem in the management-plane of the library. label Feb 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Mgmt This issue points to a problem in the management-plane of the library.
Projects
None yet
Development

No branches or pull requests

4 participants