Lambda usage
============

The lambda may be used inside the kubernetes cluster. It is available using host the same as `lambda id` and 8000 port.

The lambda may be used outside the kubernetes cluster using *luna-lamda* as proxy by
`lambda proxy requests <./_static/api.html#tag/lambda-proxy>`_.

Each lambda has its own api, whose description also available using
`get lambda documentation request <./_static/api.html#operation/getLambdaSpec>`_.

Each lambda response will contain several headers, including:

- `Luna-Request-Id` - it works in the same way as in any luna service
  (see `luna-lambda OpenAPI specification <./_static/api.html>`_ for details)

- `Lambda-Version` - contains current lambda version

There are several possibilities to get info about lambda during it works:

- to get lambda info use `get lambda <./_static/api.html#operation/getLambda>`_

- to get lambda status use `get lambda status <./_static/api.html#operation/getLambdaStatus>`_

- to get lambda logs use `get lambda logs <./_static/api.html#operation/getLambdaLogs>`_

There is possibility to stop/pause lambda using `switch lambda request <./_static/api.html#operation/switchLambda>`_. See `lambda switch <./lambda_switch>`_ for more info.

Lambda can be deleted using `delete lambda request <./_static/api.html#operation/deleteLambda>`_. Lambda pod will be stopped and deleted as well as S3 object with lambda archive.
There is also will be an attempt to remove lambda image manifest from registry in background task. Note, that it will only work if deletion is enabled in registry, otherwise
service will log failed attempt to remove image and save this message to monitoring (`lambda_errors` series). Successful manifest deletion message also will be saved to monitoring.
Deleting image manifest from registry doesn't mean that image will be deleted from registry immediately, instead is will be deleted on the next registry garbage collection run.