Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Proposal: define custom URL for functions #1082
Within the function definition we should provide an alternative configuration for when someone wants to serve a website or api from a function such as:
Imagine a microservice/function named
It would be exposed as per:
If a user would like a more user-friendly or custom URL than what they currently have by default
Cookies issued to
User currently need to do this via an ingress path in Kubernetes or a custom configuration for their reverse proxy of choice.
This proposal would allow a custom domain to be routed such as:
The way we add arbitrary metadata to functions is via annotations, such as how we define topics for the connector SDK / triggers.
functions: giving-page: image: ae/annotations:0.1 annotations: url: giving-page.com
The gateway would look for a
A query and cache for
I don't think that multiple URLs (hosts) should be specified at this point, since they will point to the same function.
In production use, the user would still have to manage and configure DNS records and TLS certificates. This change would only be concerned with reverse-proxying requests to functions.