Our deployment is breaking the proxies separation of concerns

[ACLay]

The proxy configuration is set up to separate dev from prod, internal domains and services from public ones, and websites from APIs.

However, for the proposals system, we're using the same external web proxies for both the website and the API.
This doesn't feel right. I think the API should instead be provided on the internal api proxy.

[srconway]

Is this because of the way they're deployed or just the way we've configured the proxies? What would be involved in separating them?

[TickleThePanda]

I don't think we can change where the API is deployed to so it's available to the current software - it relies on it being at the /graphql endpoint and changing this would require creating a build that defines a different URL for the API. We can consider that the GraphQL API here is part of the application.

We could add the GraphQL API endpoint to the API proxies so that it's available more clearly to developers.