[FEAT-API]: Create Lambda SOP/Documentation #611
Description
The following lifecycle issues needs to be fleshed out and documented in a README file, likely in the lambda folder itself with a reference to it in the main backend README:
i) How do I add new lambda functions?
- How do I access these new lambda functions once they are created (i.e. how do I get the endpoint?)
ii) How do I update existing lambda functions?
iii) What is the merge strategy into ci/govcloud-dev-sct-api (or other ci branches when they eventually are linked to a workflow) in order to not check in in-progress code into main?
iv) How do I decommission functions that don't need to exist anymore?
v) How long can these functions run?
vi) Best practices
- The frontend shouldn't directly invoke the lambda endpoint. A backend endpoint should be set up to interact with the lambda endpoint, which the frontend then calls, etc.
vii) How can I see what is currently deployed?
Some modifications will be need to be made to the workflow (develop-sct-govcloud-lambda.yaml) as we're only updating the Hello-World function at the moment.