AWSM: Amazon Web Services Modules – Re-usable, standardized and optimized Lambda functions ready for deployment and easy installation into serverless projects
170
stars
12
forks
source link
[Discussion] API Gateway endpoint as argument in `resources-cf.json` #3
I've got an awsm module and to implement it in a really usable manner I would want #2 and the ability to get some other values that are known in JAWS at this point.
Specifically the API Gateway endpoint.
The problem with this is if my module wants to know the API Gateway endpoint in resources-cf.json then we have a circular dependency.
resources-cf.json creates AWS Roles, API Gateway needs the AWS Roles, resources-cf.json would need API Gateway endpoint...
Any ideas on how we might work around this? We could just take this value as User Input, and let the user be the circular dependency resolver, but the information is pretty much there.
I've got an awsm module and to implement it in a really usable manner I would want #2 and the ability to get some other values that are known in JAWS at this point.
Specifically the API Gateway endpoint.
The problem with this is if my module wants to know the API Gateway endpoint in
resources-cf.jsonthen we have a circular dependency.resources-cf.jsoncreates AWS Roles, API Gateway needs the AWS Roles,resources-cf.jsonwould need API Gateway endpoint...Any ideas on how we might work around this? We could just take this value as User Input, and let the user be the circular dependency resolver, but the information is pretty much there.