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

az eventgrid event-subscription create command error #6331

Open
mumurug-MSFT opened this issue May 26, 2023 · 3 comments
Open

az eventgrid event-subscription create command error #6331

mumurug-MSFT opened this issue May 26, 2023 · 3 comments
Labels
Auto-Assign Auto assign by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Grid question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.

Comments

@mumurug-MSFT
Copy link

Related command

az eventgrid system-topic event-subscription create
az eventgrid event-subscription create

Extension name (the extension in question)

az eventgrid

Description of issue (in as much detail as possible)

In Azure Portal, we can create an event subscription for system topic with enabling dead-lettering as shown below: (doc reference)

image

However, az eventgrid system-topic event-subscription create doesn't have parameters deadletter-identity and deadletter-identity-endpoint in CLI and running results in unrecognized arguments: --deadletter-identity-endpoint /subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Storage/storageAccounts/xxx/blobServices/default/containers/egcontainer --deadletter-identity systemassigned error.

So followed az eventgrid topic event-subscription create doc and ran the following command and it also resulted in error.
Command:
az eventgrid event-subscription create --name xxx --source-resource-id "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.EventGrid/systemTopics/xxx" --endpoint-type storagequeue --endpoint "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Storage/storageAccounts/xxx/queueservices/default/queues/xxx" --deadletter-identity-endpoint "/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.Storage/storageAccounts/xxx/blobServices/default/containers/egcontainer" --deadletter-identity systemassigned

Output:
Code: InvalidRequest
Message: This event subscription operation is not supported using this API call. Please use the proper API and try again.

Any plan for supporting deadletter-identity for system topic? These parameters are available in both ARM template as well as Rest API.

@ghost ghost 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. Auto-Assign Auto assign by bot CXP Attention This issue is handled by CXP team. labels May 26, 2023
@yonzhan
Copy link
Collaborator

yonzhan commented May 26, 2023

Thank you for opening this issue, we will look into it.

@ghost ghost added the Event Grid label May 26, 2023
@PramodValavala-MSFT PramodValavala-MSFT self-assigned this May 30, 2023
@PramodValavala-MSFT
Copy link
Contributor

@mumurug-MSFT Thanks for the feedback! We will review and get back to you.

@PramodValavala-MSFT PramodValavala-MSFT removed their assignment Sep 28, 2023
@PramodValavala-MSFT PramodValavala-MSFT added Service Attention This issue is responsible by Azure service team. and removed CXP Attention This issue is handled by CXP team. labels Sep 28, 2023
@microsoft-github-policy-service
Copy link
Contributor

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @jfggdl.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Assign Auto assign by bot customer-reported Issues that are reported by GitHub users external to the Azure organization. Event Grid question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Service Attention This issue is responsible by Azure service team.
Projects
None yet
Development

No branches or pull requests

3 participants