Destination endpoint not found or invalid trigger type - Pick one :-( #11686
gpuchtel-grubbrr
started this conversation in
Authoring Help
Replies: 1 comment
-
The capitalization of the type attribute is wrong in your code. It should be this:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Version: Bicep CLI version 0.20.4 (c9422e0)
Description: Destination endpoint not found when trying to deploy EventGridTopic Subscription.
Detailed Message: "code":"Endpoint validation","message":"Destination endpoint not found."
I have the following Bicep definition:
If I change the 'type' from 'EventGridTrigger' to 'HttpTrigger' (for diagnostic purposes) it fails, but for a different reason:
Detailed Message: "code":"Unsupported Azure Function Trigger","message":"Can't add resource; Azure Event Grid supports EventGrid Trigger type only."
Now, for Azure to know that one must assume that Azure found the endpoint! So why does Azure complain that it is not found (in the first case) when configured correctly with EventGridTrigger. (as shown).?????????
What am I missing?
Note: the function app containing the function is created elsewhere; hence, the 'existing' declaration above
Beta Was this translation helpful? Give feedback.
All reactions