Recent searches

No recent searches

Search options

Not available on dice.camp.
dice.camp is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon server for RPG folks to hang out and talk. Not owned by a billionaire.

Administered by:

Server stats:

1.5K
active users

dice.camp: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.2

#azurefunctions

0 posts0 participants0 posts today
*
Anthony Steele

#azure #azurefunctions on #dotnet 8.0 in-process news:

techcommunity.microsoft.com/t5

It's still going to happen!

"The in-process model for .NET 8 is a top priority for the Functions team, and we hope to communicate a timeline for release soon."

The update is that there's going to be an update.

But "Even if you choose to leverage the in-process option for .NET 8 once it’s available, you should still start planning on a migration to the isolated worker model during the .NET 8 support window."

TECHCOMMUNITY.MICROSOFT.COM.NET on Azure Functions – March 2024 roadmap update Learn about updates to the isolated worker model and the roadmap for .NET on Azure Functions.
Moof! 🏳️‍🌈

If you work with #AzureFunctions that are deployed using #Devops Pipelines or #GithubActions, be aware that the function reads its data from a zip file that is deployed onto the associated storage account, and access to that zip file is controlled by a SAS token, and that token has an expiry date.

Today I've been caught out by this because a Functions app that I wrote in 2022 has been working tirelessly well since then, and hasn't required updating, and suddenly the runtime couldn't load the code to execute, because the SAS token had expired, and the service stopped working.

Redeploying the app solved the problem. I've just run through all my pipelines that were last deployed in 2022 and redeployed them to ensure they have a fresh token.

Check your old pipelines, see if you need to run a redeployment today.

TrendingLive feeds
About