Presently, routes are handled via {proxy+}, which is bad for a number of reasons, and really was a stepping stone until a better solution was made. The better solution is as follows:
On DEPLOY:
Allow for selection of target env. Read config by lookup from API caller.
Example command should say something like "Please publish this graph version 2345 to env STG"
- Crete CodeBuild artifacts that get deployed to app named lambda layers or EC2/Fargate, package scheduler/graph.
- Use CodeDeploy to build or sync a deployment group (CodeDeploy parlance).
- Report status via web sockets.
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CodeBuild.html
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CodeDeploy.html
Presently, routes are handled via {proxy+}, which is bad for a number of reasons, and really was a stepping stone until a better solution was made. The better solution is as follows:
On DEPLOY:
Allow for selection of target env. Read config by lookup from API caller.
Example command should say something like "Please publish this graph version 2345 to env STG"
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CodeBuild.html
https://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/CodeDeploy.html