Skip to content

Support mode to generate queueUrl from incoming request, rather than static hostname. #219

@nhoughto

Description

@nhoughto

The current behaviour as I understand it is to configure a static hostname (or allow it to default to localhost) and then that value is used to create the queueUrl that clients will follow to do SQS ReceiveMessage etc.

This works in simple situations but breaks scenarios where a single goaws instance might have multiple ingress paths, think Kubernetes Service vs Kubernetes Ingress vs Kubernetes NodePort.. there are lots of reasons this can happen.

To solve this problem it would be great if you could configure a mode where the hostname used in the queueUrl is derived from the incoming request rather than from configuration or defaulted. This limits the number of "environments" you can have, I expect you can only have 1 in "derive" mode, but i'd expect most users have just one environment anyway.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions