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] Microsoft.ContainerRegistry @ 2023-07-01 - IdentityProperties for CredentialSets define identity modes not supported by the API #32154

Open
stephybun opened this issue Jan 15, 2025 · 1 comment
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that

Comments

@stephybun
Copy link

API Spec link

API Spec version

2023-07-01

Describe the bug

The spec defines support for UserAssigned and SystemAssigned, UserAssigned identities for CredentialSets, but when trying to create a Credential Set with either of these identity modes an API error is returned:

{
  "error": {
    "code": "CannotSetResourceIdentity",
    "message": "Resource type 'Microsoft.ContainerRegistry/registries/credentialSets' does not support creation of 'UserAssigned' resource identity. The supported types are 'SystemAssigned'."
  }
}
{
  "error": {
    "code": "CannotSetResourceIdentity",
    "message": "Resource type 'Microsoft.ContainerRegistry/registries/credentialSets' does not support creation of 'SystemAssigned, UserAssigned' resource identity. The supported types are 'SystemAssigned'."
  }
}

Expected behavior

That only SystemAssigned is defined for the type field in IdentityProperties, or the API is updated to support these modes.

Actual behavior

Identity types are defined that are not supported by the API

Reproduction Steps

Try and create a Credential Set resource with UserAssigned or SystemAssigned, UserAssigned Identity via the API

Environment

No response

@stephybun stephybun added the bug This issue requires a change to an existing behavior in the product in order to be resolved. label Jan 15, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added question The issue doesn't require a change to the product in order to be resolved. Most issues start as that customer-reported Issues that are reported by GitHub users external to the Azure organization. labels Jan 15, 2025
@v-jiaodi v-jiaodi added the Mgmt This issue is related to a management-plane library. label Jan 16, 2025
@v-jiaodi
Copy link
Member

@AntonioVT Please help take a look, thanks.

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. customer-reported Issues that are reported by GitHub users external to the Azure organization. Mgmt This issue is related to a management-plane library. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that
Projects
None yet
Development

No branches or pull requests

3 participants