Helm-Deployed Agent Planes cannot communicate with connectors/control planes over http (only https).
This is due to a default url allowance configuration which requires https as the protocol scheme.
This cannot be easily overriden (need to use envVar section).
Furthermore, calling a consumer-only skill with a sparql-result body will fail because of unbound value bindings (sended text is not bound, parameters in body have been read from request and will not be bound again).
Calling a consumer-only skill with a runMode ALL will work, but is executed on the PROVIDER side. That is wrong
the helm chart of the agent planes should have explicit values in the agent.services.connector section in order to override the default allowance regexes.
Steps To Reproduce
Deploy helm chart an use non-ingress control plane reference
Current Behavior
Helm-Deployed Agent Planes cannot communicate with connectors/control planes over http (only https). This is due to a default url allowance configuration which requires https as the protocol scheme. This cannot be easily overriden (need to use envVar section).
Furthermore, calling a consumer-only skill with a sparql-result body will fail because of unbound value bindings (sended text is not bound, parameters in body have been read from request and will not be bound again).
Calling a consumer-only skill with a runMode ALL will work, but is executed on the PROVIDER side. That is wrong
see https://github.com/eclipse-tractusx/knowledge-agents/issues/150
Expected Behavior
the helm chart of the agent planes should have explicit values in the agent.services.connector section in order to override the default allowance regexes.
Steps To Reproduce
Deploy helm chart an use non-ingress control plane reference