A serverless function that is not serverless at all

ukitdog
2 min readJul 15, 2022

--

Nowadays, using Serverless resources are the way to low down the infrastructure maintenance cost, engineer can focus on the business logic and bypass all the complex setting in the cloud.

However, there is no Blackmagic for any tech and we need to understand the life cycle of each service provider.

For instance, I set up a project to retrieve an API key from env var and expect the API key is stored at the secret manager.

In this way, It is expected that the API key will be automatically loaded to the latest version if I do not assign the version of the secret and the Lamda function at the application level does not need to care about how to reload or retrieve the newest one from the OS level.

However, It is not always true at the Azure function app at I do carry the expectation from another service provider like GCP cloud run which is Knative based and the secret is mount via injection each new version will auto trigger a deployment from the controller and I really do not need to care how can I handle it.

Lesson learn:

Never trust any Lamda function and dig into the detail or the tech involve under the hood

Reference:

  1. https://github.com/MicrosoftDocs/azure-docs/issues/51708
  2. https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references?tabs=azure-cli#rotation

Sign up to discover human stories that deepen your understanding of the world.

Free

Distraction-free reading. No ads.

Organize your knowledge with lists and highlights.

Tell your story. Find your audience.

Membership

Read member-only stories

Support writers you read most

Earn money for your writing

Listen to audio narrations

Read offline with the Medium app

--

--

ukitdog
ukitdog

No responses yet

Write a response