Durable Functions Support for PowerShell about azure-functions-powershell-worker HOT 42 CLOSED

Currently work in progress.

from azure-functions-powershell-worker.

We'll be working on this very soon. Not ready to commit to any specific date yet. Thank you for your votes!

from azure-functions-powershell-worker.

Durable PowerShell support (preview scope: Function Chaining, Fan-Out/Fan-In, Async HTTP APIs patterns) is deployed to Azure.

In order to try it out, please switch your app to PowerShell 7 by following these instructions: #371 (comment).

You can find the samples for Function Chaining and Fan-Out/Fan-In patterns here: https://github.com/Azure/azure-functions-powershell-worker/blob/dev/docs/durable-experimental-instructions.md#2-sample-app.

We will continue working on the rest. The GA timeline and the implementation completeness depend on your feedback very much! Thank you!

from azure-functions-powershell-worker.

I think people are going to hate me, I want to discuss this in terms of priority.

First, we need to get PowerShell support onto AzureFunctions 2.0 and GA.

Then, there are several much nicer to haves:

• Import from PS Gallery
• Object, streaming arguments (not serialized strings)
• Managed Service Identity support
• Azure KeyVault support, like Azure Automation - would this be a binding that's custom and generic across all 2.0 function languages?
• I even think if we have well defined PowerShell functions with arguments, the Swagger generation should be automatic.
• I also want better PowerShell logging support

And of course Durable Functions, I want this too, but I suspect Durable Functions syntax in PowerShell might be a bit messy. I don't know how async/await will look like, and traditionally PowerShell async is done with Jobs or Runspaces, so I'm curious what a prototype would look like.

So let me be the first in the thread to say we need PS+DF but may be lower in priority. I don't know if we need this day 1 of PS on 2.0

from azure-functions-powershell-worker.

If you want to try this out, see the instructions.

from azure-functions-powershell-worker.

Added my +1. Powershell functions lend themselves to long running process, and since we don't have workflows in PS Core, durable functions is a natural replacement.

from azure-functions-powershell-worker.

Welp, I don't know what I did differently on the third attempt, might have just required a break to avoid missing a step.

All working now (and working well!) Good job all that've worked on this.

from azure-functions-powershell-worker.

I would be interested in getting feedback from people who have tried durable functions supported in AzF today (C#, for example) and are familiar with the development experience. Essentially, your orchestrator script maintains state while the activity functions are stateless. However, there are other ways to maintain state across multiple functions to replace the need for a single monolithic script.

from azure-functions-powershell-worker.

I agree with @johnnliu. In my opinion, Powershell support for Azure Function V2 would come first and then other things like Durable Functions.

Please make PS support for Azure Functions V2... please...

from azure-functions-powershell-worker.

Can we even just have the ability to have Activity functions in PowerShell?

I can see why the orchestrator function might have to stay out of PS due to the stuff it does with "await". However, I think that the biggest utility for PS would be in the Activity function especially when dealing with Azure automation.

@bytemech I had the same idea for mixing a C# client + orchestrator but calling into a PowerShell ActivityTrigger. Have you tried this yet with the preview release?

from azure-functions-powershell-worker.

I'm trying both FanOutFanInStart and FunctionChainingStart. Getting the 404 in the Test/Run pane in the Portal:

Also using the function url (both in Windows PowerShell and PowerShell 7):

Will try tearing it down and starting again later on tonight.

from azure-functions-powershell-worker.

I see. Thanks for the info. Great job on durable functions so far!

from azure-functions-powershell-worker.

@JustinGrote We've recently added more samples, all the major patterns and features are supposed to be covered. There are still some minor gaps in both the docs and the implemented features. Please let us know if you find that something important is missing.

from azure-functions-powershell-worker.

@JustinGrote You are right, the Tutorials section is not updated yet. These topic are supposed to be mostly covered by https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-overview?tabs=powershell. But thank you for pointing this out, we'll take care of it.

from azure-functions-powershell-worker.

Does really need a vote 😜. Definitely would love this to happen.

from azure-functions-powershell-worker.

Yes ...yes please!

from azure-functions-powershell-worker.

yes absolutely!

from azure-functions-powershell-worker.

Absolutely a great idea. I do everything ps

from azure-functions-powershell-worker.

OOh, yes please. Love that idea. Plus 1 to JustinGrote's comments.

from azure-functions-powershell-worker.

Yes please, we need this at a customer of mine. 👍

from azure-functions-powershell-worker.

Yes !!!

from azure-functions-powershell-worker.

Yes, please!

from azure-functions-powershell-worker.

Yes!! We need PowerShell support!

from azure-functions-powershell-worker.

For implementation, what seems most logical to me is to expose the orchestrator object in a variable, just like $req, initially. Later powershell functions as wrappers around the methods could make it more user friendly.

from azure-functions-powershell-worker.

Can we even just have the ability to have Activity functions in PowerShell?

I can see why the orchestrator function might have to stay out of PS due to the stuff it does with "await". However, I think that the biggest utility for PS would be in the Activity function especially when dealing with Azure automation.

from azure-functions-powershell-worker.

I think following the javascript worker's example is a good first step: https://github.com/Azure/azure-functions-durable-js

from azure-functions-powershell-worker.

any update on this?

from azure-functions-powershell-worker.

Since PowerShell support for Azure functions is now GA, any updates on Durable Functions support for PowerShell?

from azure-functions-powershell-worker.

Any update on this guys? Is MS planning on adding support for this?

from azure-functions-powershell-worker.

@Abdul-Sen please see Anatoli's comment above. #77 (comment)

We can confirm that we have started to work on it. We have non-production supported early prototype implementation for the chaining pattern. If you would like to try it contact @AnatoliB

from azure-functions-powershell-worker.

Any Update?

from azure-functions-powershell-worker.

Please try this out, and thank you for your feedback!

from azure-functions-powershell-worker.

How soon until this feature for PowerShell support goes GA? Could you provide a ball park date? Thank you!

from azure-functions-powershell-worker.

I made a quickstart to help get started with this:
https://gist.github.com/JustinGrote/63983c9a53b4085d4710befea17bc913

from azure-functions-powershell-worker.

I've updated the instructions at https://github.com/Azure/azure-functions-powershell-worker/blob/dev/docs/durable-experimental-instructions.md with all the steps required to try this out on Azure.

from azure-functions-powershell-worker.

Has anyone got this working in Azure?

I have trouble running Functions locally in general (laptop needs a re-image... my problem) so I'm jumping straight to Azure. With both the Chaining and Fan-Out/Fan-In examples I end up with a 404.

from azure-functions-powershell-worker.

@Windos I've got this working in Azure :-) Please tell us more: how do you get a 404? Which function do you start and how? Are you using a correct URL (please keep in mind that the URLs in the instructions are for the local host only.

from azure-functions-powershell-worker.

I tried this on Azure and most things seemed to be working but the command Start-DurableTimer seems to not be available in Azure. I can see that it is exported from Microsoft.Azure.Functions.PowerShellWorker.psd1 in the git repository but not when I'm running in Azure. What can I do to make this available?

from azure-functions-powershell-worker.

@SimonWahlin Start-DurableTimer has been implemented just a couple of days ago. It normally takes 2-4 weeks for worker updates to be deployed to the Azure Functions service, so expect Start-DurableTimer to be available by the end of August.

from azure-functions-powershell-worker.

Thank you everyone for your patience, feedback, and contributions! PowerShell support in Durable Functions is now generally available. As always, your feedback is very welcome.

from azure-functions-powershell-worker.

@AnatoliB great achievement! Will the examples docs be updated?

from azure-functions-powershell-worker.

@anatolliB none of the examples in this section have Powershell equivalents, am I looking in the wrong place?
https://docs.microsoft.com/en-us/azure/azure-functions/durable/durable-functions-sequence?tabs=csharp

from azure-functions-powershell-worker.