View at Medium.com

The above is an article with a script that looks similar to what we have been using to get iex access to k8s

I have been receiving daily reports via email that I would like to put into a dashboard.
This seems to be the piece of the puzzle that will allow it to be moved to AWS lamdba.

https://docs.aws.amazon.com/ses/latest/dg/receiving-email-action-lambda-event.html

Recently I moved an API integration to use Oban (https://hex.pm/packages/oban).

Previously we had been making API calls to a third party that we need to notify of changes. Our old implementation simple made the call and logged errors. This meant we had to spend time checking logs for possible problems.

After the move to Oban (we use the paid for add-on Oban Web) items needing attention now have a UI.

I have not yet worked out how best to model “wait for an email then retry”.

This is the magic incantation you need:

kubectl exec -it $(kubectl get pods | grep PROJECT_DEPLOYED_NAME | head -1 | awk '{print $1}') -- bash -c "/app/bin/PROJECT_NAME remote"