Describe the bug
asyncapi binding generate & inject guarded config in route based on Security schema available in http-asyncapi spec. It expect the guard to be named as String.format("%s:jwt0", config.namespace) for example: zilla-http-kafka-asyncapi:jwt0.
However, zilla schema restricts naming of guard with a : in the name. So zilla instance crash with mentioned error:
[11,4][/guards/zilla-http-kafka-asyncapi:jwt0] The object must not have a property whose name is "zilla-http-kafka-asyncapi:jwt0".
error
io.aklivity.zilla.runtime.engine.config.ConfigException: Engine configuration failed
...
at io.aklivity.zilla.runtime.command/io.aklivity.zilla.runtime.command.internal.ZillaMain.main(ZillaMain.java:34)
Caused by: io.aklivity.zilla.runtime.engine.config.ConfigException: [11,4][/guards/zilla-http-kafka-asyncapi:jwt0] The object must not have a property whose name is "zilla-http-kafka-asyncapi:jwt0".
... 8 more
To Reproduce
Steps to reproduce the behavior:
- Start zilla with guard config as
zilla-http-kafka-asyncapi:jwt0.
- See above mentioned error
Expected behavior
Zilla should be able to handle asyncapi binding with guard enabled.
Screenshots
Issue:

Proposed Fix:

Describe the bug
asyncapibinding generate & injectguardedconfig inroutebased on Security schema available inhttp-asyncapispec. It expect theguardto be named asString.format("%s:jwt0", config.namespace)for example:zilla-http-kafka-asyncapi:jwt0.However,
zillaschema restricts naming ofguardwith a:in the name. Sozillainstance crash with mentioned error:To Reproduce
Steps to reproduce the behavior:
zilla-http-kafka-asyncapi:jwt0.Expected behavior
Zilla should be able to handle asyncapi binding with guard enabled.
Screenshots
Issue:

Proposed Fix:
