However, when that container is alive, we're getting 404 Not Found error. (When the container is still PENDING or is otherwise deemed "not in service" by ECS, ALB responds with 503 Service Unavailable.)
Last year we had to do some monkey business to get the container to answer to requests for /route (e.g. 2017 Budget API listens for requests to /budget and routes those to the default app, which then sub-routes to the various API endpoints below that e.g. /budget/code).
Not sure if this is an issue with the routing in the various urls.py files that each project has (one for the global Django project, and one each for the Django apps within the project), or if this is a problem with Swagger.
Currently the Disaster Resilience project is deployed, and we have a live container answering to the request for http://service.civicpdx.org/disaster-resilience.
However, when that container is alive, we're getting 404 Not Found error. (When the container is still PENDING or is otherwise deemed "not in service" by ECS, ALB responds with 503 Service Unavailable.)
Last year we had to do some monkey business to get the container to answer to requests for /route (e.g. 2017 Budget API listens for requests to
/budgetand routes those to the default app, which then sub-routes to the various API endpoints below that e.g./budget/code).Not sure if this is an issue with the routing in the various
urls.pyfiles that each project has (one for the global Django project, and one each for the Django apps within the project), or if this is a problem with Swagger.Projects: