- There is no authentication that can be added here. This storage is meant for referencing additional material needed to complete a deployment or soon after post-deployment.
- I don't recall the exact timeline for the package, but the storage is not long-term. Should an app need components long term, they should be moved to a deployed blob container in the app that will persist and could be referenced later.
Azure Managed Application - reliable way to deploy .NET code to Azure Function
Cezary Klus
1
Reputation point
Wonder if anyone can share production experiences regarding safe and reliable way of deploying code to Azure Function (Linux Consumption Plan) within the Azure Managed Application. I've found an official sample here that uses WEBSITE_RUN_FROM_PACKAGE setting pointing to the staging storage of the Managed Application based on
deployment().properties.templateLink.uri
Is that storage:
- Secure? By this example absolutely not - it is based on public access as there is no SAS token added. How to achieve SAS token security - lifetime should be maxed out?
- Persistent? Other words - not ephemeral that will be ultimately deleted.
ZipDeploy from the application definition artifacts is not an option as it is not supported on Linux Consumption plans. Neither MSDeploy of course.
Thanks
1 answer
Sort by: Most helpful
-
Evan Hissey 1 Reputation point Microsoft Employee
2022-05-13T23:14:52.46+00:00