Closed shreddedbacon closed 5 months ago
IANA has an appspecific
URI suffix for this purpose that you might be able to use. I guess it would be something like /.well-known/appspecific/sh.lagoon.discovery.json
?
IANA has an
appspecific
URI suffix for this purpose that you might be able to use. I guess it would be something like/.well-known/appspecific/sh.lagoon.discovery.json
?
Yeah, that can work too
Just would have been nicer to use /.well-known/lagoon
from a vanity perspective :sparkles:
General Checklist
Database Migrations
Just a simple way to expose some discovery data via a
/.well-known/appspecific/sh.lagoon.discovery.json
endpoint.This could expose other information too, and for tools like
lagoon-cli
andlagoon-sync
, users only need to know the API hostname (and maybe port if not standard http/s) when configuring their tools, rather than needing to know all the other endpoint information.This contains some basic information like so, as long as the variables are provided to populate it correctly. Some are already provided by the chart, others will need to be created in the chart
This requires updates to the charts to inject
SSH_TOKEN_ENDPOINT
andSSH_TOKEN_ENDPOINT_PORT
variables that require a user to define, theport
may be able to be consumed via the chart though, so only the hostname would need to be provided.Conditions for the endpoint DNS record would be if this is a fresh install of the token or ssh service, the cluster loadbalancer/service IP or name for the token endpoint may not be known immediately, so could be set to the DNS record that will eventually be populated once the loadbalancer/service IP is know after deployment.