-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[public-api] Route api.<domain> to public api service & deployment #9363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
875bef7
to
09d6121
Compare
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-mp-papi-caddy.4 |
/werft run with-clean-slate-deployment=true 👍 started the job as gitpod-build-mp-papi-caddy.5 |
if err := register(srv); err != nil { | ||
logger.WithError(err).Fatal("Failed to register services.") | ||
} | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this change necessary to set up the routing or just overlooked in earlier PRs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overlooked from other PRs.
/unhold |
Description
Related Issue(s)
How to test
Navigate to preview build. Prepend
api.
to the URL and you should seehello world
https://api.mp-papi-caddy.staging.gitpod-dev.com
In prod, we haven't configured the DNS record to point to our loadbalancer so it won't work, yet. This is fine, we can iterate in preview for now.
Release Notes
Documentation
NONE
/hold