You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, every time you deploy a script, a new script folder is created with the new code. This is what let's you, more or less, or load a new script on to the Azure Functions instance. So, it's a feature.
But it's undesirable to leave the old code there forever. The primary reason for this is that we cannot reliably tell if old code is loaded or not. If it is loaded, we cannot reliably delete it.
So, when the first function is run we should check if there are lingering script folders that could be deleted and attempt to delete them. Eventually this will trim out old code but it may take some time because we don't know reliably when a Azure Function instance is restarted.
The text was updated successfully, but these errors were encountered:
Right now, every time you deploy a script, a new script folder is created with the new code. This is what let's you, more or less, or load a new script on to the Azure Functions instance. So, it's a feature.
But it's undesirable to leave the old code there forever. The primary reason for this is that we cannot reliably tell if old code is loaded or not. If it is loaded, we cannot reliably delete it.
So, when the first function is run we should check if there are lingering script folders that could be deleted and attempt to delete them. Eventually this will trim out old code but it may take some time because we don't know reliably when a Azure Function instance is restarted.
The text was updated successfully, but these errors were encountered: