Closed
Description
It seems like localstack runs a proxy
Starting multi API server process on port 51492
but there is no documentation on this service. Looking at the code, it seems like it's purpose is only to list what services local stack is running?
curl http://localhost:51492/servers
{"__server__": {"port": 51492, "thread": null}, "apigateway": {"port": 4566, "thread": null}, "cloudwatch": {"port": 4582, "thread": null}, "ec2": {"port": 4556, "thread": null}, "iam": {"port": 4557, "thread": null}, "logs": {"port": 4553, "thread": null}, "redshift": {"port": 4577, "thread": null}, "route53": {"port": 4580, "thread": null}, "s3": {"port": 4563, "thread": null}, "secretsmanager": {"port": 4552, "thread": null}, "ses": {"port": 4551, "thread": null}, "sns": {"port": 4562, "thread": null}, "ssm": {"port": 4583, "thread": null}, "sts": {"port": 4592, "thread": null}, "events": {"port": 4554, "thread": null}}
If this is all, would it be out of line to open a PR to make this proxy act as a general purpose ingress for all the endpoints?
Edit: looks like there is a dedicated project to achieve what I'm asking, but I'd bet a lot of magic internet points (that's what we all work for, right?) that I'm not the only one that would rather have this built in.
Metadata
Metadata
Assignees
Labels
No labels