You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The listeners created from Async API has the following init function:
function init(ListenerConfiglistenerConfig , int|http:ListenerlistenOn) {}
The ListenerConfig record only has the trigger specific configurations, and if you want to configure the HTTP listener config then you need to pass the HTTP listener as the listenOn parameter(this requires a HTTP listener defintion). There is no way to simply give the port for listenOn and add the HTTP configurations separately.
Suggested Improvement
In case of GraphQL listener, we can pass the HTTP listener configurations as part of GraphQL listener configurations:
# Provides a set of configurations for configure the underlying HTTP listener of the GraphQL listener.publictypeListenerConfigurationrecord {|*http:ListenerConfiguration;
|};
This approach is more preferable than the other
Version
Ballerina SwanLake Update 11
The text was updated successfully, but these errors were encountered:
TharmiganK
changed the title
Provide a way to configure the HTTP Listener configurations in the Aync API generated listeners
Provide a way to configure the HTTP Listener configurations in the Async API generated listeners
Jan 8, 2025
Current Limitation
The listeners created from Async API has the following init function:
The
ListenerConfig
record only has the trigger specific configurations, and if you want to configure the HTTP listener config then you need to pass the HTTP listener as thelistenOn
parameter(this requires a HTTP listener defintion). There is no way to simply give the port for listenOn and add the HTTP configurations separately.Suggested Improvement
In case of GraphQL listener, we can pass the HTTP listener configurations as part of GraphQL listener configurations:
This approach is more preferable than the other
Version
Ballerina SwanLake Update 11
The text was updated successfully, but these errors were encountered: