Miserlou / Zappa

Serverless Python
https://blog.zappa.io/
MIT License
11.89k stars 1.2k forks source link

Feature: Ability to use existing API Gateway #1576

Open bharling opened 6 years ago

bharling commented 6 years ago

Context

Hi, we're a small company in the process of gradually expanding our monolithic elasticbeanstalk application with smaller targeted microservices based on ApiStar / Zappa. We're getting good mileage so far and have deployed a small selection of background task-type services using SNS messaging as triggers, however we'd really like to start adding actual endpoints to our stack that call lambda functions. I've been trying for a couple of days to figure out how to properly setup an API gateway that will proxy to both our existing stack and newer services deployed with zappa. I've tried manually setting up a custom domain for the zappa apps and a cloudfront distro in front of both the existing stack and the new api gateway but am not getting very far. It would be a lot simpler IMO if we could specify an existing API gateway ARN in the zappa_settings.json and elect to use that so that it could integrate with an existing configuration.

Expected Behavior

Would be great if I could specify "api_gateway_arn" in the zappa_settings.json file to use an existing api gateway

Actual Behavior

There is no option to do this

Possible Fix

I guess this is not straightforward given the API gateway is created via a cloudformation template, I guess it'd require moving some of that to boto functions instead ?

Steps to Reproduce

N/A

Your Environment

Smaxor5 commented 4 years ago

Guessing this never happened. cool cool