question

Kevin avatar image
Kevin asked

Azure: ExecuteFunction must be updated for the 'Isolated Worker' model

We started our Azure Functions project for custom PlayFab cloud scripts roughly a year ago. At the time, the documentation led us to create a Functions app using the 'In-Process' model on Azure.

Microsoft now recommends migrating all Functions apps to the 'Isolated Worker' model. We're starting to go through this migration process, but there is a snag. Our Azure Functions project uses the ExecuteFunction script for local testing as described in the PlayFab documentation. However, the ExecuteFunction script was written for the In-Process model and can't be used as-is for the Isolated Worker model. While I'm finding that it's easy to migrate our own functions using the migration guide, it's not as obvious how to migrate ExecuteFunction.

The QuickStart tutorials now guide you to create an Isolated Worker function app, so developers who are new to PlayFab will encounter this same issue

CloudScript
10 |1200

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

0 Answers

·

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.