add action-style templating of webhook URL for event trigger and remote schemas

[marionschleifer]

So far, when creating an event trigger and select a webhook url, we have the option to use environment variables but we cannot use string templates yet. Add support to be able to use string templates.

[tirumaraiselvan]

TBD:

1. What are the constraints on the template?

Do we allow ${WEBHOOK_BASE_DOMAIN}/hook-1 and also http://something.com/${NAMESPACE}/hook-2

2. What is the templating syntax? BASH like variable expansion?
   So ${WEBHOOK_BASE_DOMAIN}/hook-3 is different from ${WEBHOOK_BASE}_DOMAIN/hook-3

[flybayer]

I would very much appreciate this feature! Currently I'm adding a new env variable for every single event.

[carllippert]

+1 This would be an excellent addition for those heavily leaning on events and solve some of the whole metadata swaps people have been talking about to get around env var problems with migrations

[gunar]

Alternative: The payload includes trigger.name so you could point all events to a single endpoint and do the routing on the server side.

if (payload.trigger.name === "user_added") {
  // ...
} else if (payload.trigger.name === "user_removed") {
  // ...
} else {
  throw Error("unexpected event");
}

[jchonde]

I would expect the webhook url to behave like the action's http handler. eg: {{SERVICE_BASE_URL}}/my_endpoint
That would make things consistent if not useful.

[tirumaraiselvan]

Yes, making it consistent is definitely something that should be done. The webhook key in event trigger APIs can take a templated url, just like in Actions. The webhook_from_env key remains unchanged for backward-compatibility.

Changing title to reflect this feature

[amille14]

@tirumaraiselvan is your last comments saying that this already exists for the webhook key for event triggers, or just that it is a planned feature? I need this feature as well to enable working with a vercel serverless api for my events. Having it work exactly like action webhook templated urls would be great.

When I tested it on v1.2.2 it didn't seem to work for events.

[rikinsk]

@amille14 This is not available now. Its a planned feature.

[sahanatroam]

similar issue: #5090

[dan-lee]

@gunar That's a great workaround! Should be easy to migrate after this feature's available

[ancs21]

Hello @rikinsk ,

Amazing method for DX.
Currently, my team is migrating manual metadata.

Please update ASAP. Thanks.

[nksaraf]

Would love to have this feature!! Using remote schemas and events extensively.

[smblee]

What's the status on this issue? I see the pull request but I am unable to use handlebars to set the URLs still

[ancs21]

@smblee I think this feature release in the next version.

[adventurini]

Is this feature released yet?

[picosam]

@tirumaraiselvan I'm unable to use this even though you supposedly released it in v1.3.3 -- am I missing something?

[kedarguy]

@adventurini @tirumaraiselvan It's working for me on 1.3.3

[tobiastornros]

Thanks for including this in 1.3.3 @tirumaraiselvan

I think that both Hasura UI and Docs should be updated to reflect this change.

Here is how you use it @adventurini @picosam

[picosam]

Ohhhh so we should use URL. Sorry, I kept using environment variables!

[adventurini]

Yes, I was doing the same thing @picosam. Also, docs should be updated for the current language of:

Alternatively, environment variables can also be read from the .env file, created manually by the user, at the **_project root directory._** A global flag, --envfile, is available to explicitly get the .env file created by the user, which defaults to .env if no flag is provided.

The project root directory is confusing. It should state the hasura generated root directory -- I also understand that many people will understand the difference and what the docs meant, but it is still not clear.

[ericxiao251]

Hey folks, is there an example of the env file structure? I'm getting Value for environment variables not found: errors when trying to access my webhook. This is an example URL:

{
  "SOME_WEBHOOK_URL": "https://some_url",
}