Closed faxioman closed 4 years ago
Ok, the reason for this behaviour is now clear:
case 'http':
// TODO: Rely on Kubeless httptrigger object when it support paths
break;
Has this implementation already started? The httptrigger is supporting paths now.
yes, that's correct but we never had the time to implement that. Accepting contributions here!
@andresmgot ok, I'm preparing a pull request
Ok, pull request pushed: https://github.com/serverless/serverless-kubeless/pull/206
I see that the plugin is directly creating an http ingress instead of creating a kubeless http trigger. Is there a chance that this odd behaviour will change in the near future?
Thanks!