Azure EventGrid trigger not supporting NextLink in KeyVault API
- Dominant language
- TypeScript
- Stars
- 111
- Forks
- 109
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 20
Description
### Describe the Bug with repro steps
1. Create workflow (Consumption or Standard)
2. Create EventGrid trigger (When a resource event occurs)
3. Select KeyVaults resource type and subscription
4. Attempt to select Keyvault
Workaround: Using the KV full URI works, the trigger does not fail.
### What type of Logic App Is this happening in?
Standard (Portal)
### Which operating system are you using?
Windows
### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
### Workflow JSON
```json
{
"definition": {
"$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",
"actions": {},
"contentVersion": "1.0.0.0",
"outputs": {},
"triggers": {
"When_a_resource_event_occurs": {
"type": "ApiConnectionWebhook",
"inputs": {
"host": {
"connection": {
"referenceName": "azureeventgrid"
}
},
"body": {
"properties": {
"topic": "XXX",
"destination": {
"endpointType": "webhook",
"properties": {
"endpointUrl": "@listCallbackUrl()"
}
},
"filter": {
"includedEventTypes": [
"Microsoft.KeyVault.KeyExpired"
]
}
}
},
"path": "/subscriptions/@{encodeURIComponent('SUBSCRIPTIONID')}/providers/@{encodeURIComponent('Microsoft.KeyVault.vaults')}/resource/eventSubscriptions",
"queries": {
"x-ms-api-version": "2017-09-15-preview"
}
},
"splitOn": "@triggerBody()"
}
}
},
"kind": "Stateful"
}
```
### Screenshots or Videos
Not all Keyvaults are listed.
After a certain number, the API is paging the resources and the UI is not listing the KeyVaults as expected.
Example, KV 6 and 7 are listed only in NextLink, but UI is not picking them up.
UI:

API Results:

NextLink:

KeyVault Listing:

### Browser
Edge
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
No repository files or tests are named. Reproduce the EventGrid trigger resource selection with enough KeyVaults to produce a NextLink, then trace the UI's KeyVault listing and pagination response; done when all resources returned across pages, including KV 6 and 7, are selectable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, react, typescript
- Domain
- cloud, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100