WireMock

It just means that you can’t access system or env vars via Handlebars templating in the webhook fields that support it.

This might actually be obsolete now that webhooks has moved to the core, so worth giving it a try.

Please let me know what you find out, because if it’s changed I’ll delete that from the docs

I tried the `systemValue` Handlebars helper with a system property in the method field, and after calling `Webhooks.applyTemplating()` on the `WebhookDefinition`  the method field value becomes `[ERROR: Access to my.custom.property is denied]`.

Did you permit that property to be used in your startup configuration?

I was not aware that that was needed. Let me look into that part.

As I see, `Webhooks` is always initialized with <https://github.com/wiremock/wiremock/blob/master/src/main/java/org/wiremock/webhooks/Webhooks.java#L68|TemplateEngine.defaultTemplateEngine()>, thus the `TemplateEngine` it uses is always initialized with null `permittedSystemKeys` . and never permits any keys.

Ah, I thought I’d updated it to use injection. We can change that in the next release, then this will work.]