Matthew Fisher comments

Results 116 comments of


                                            Matthew Fisher

Only one newly created managed identity appears in the user assigned node of the Function App when 2 managed identities were created and assigned at the same time

Does refreshing fix the issue?

Fail to execute "Execute Function Now..." action for "durableHello1HttpStart" function

I need to figure out if this should be supported / what kind of experience it would look like. I'll touch base with Nathan (when he gets back) and Matt

Don't add custom `AzureWebJobsStorage` emulator string if nothing changed

We may want to consider adding additional logging here as well.

Reduce the number of connection setup prompts when debugging

Should probably be done in tandem with #4694 because wizards will need to be merged if we decide to consolidate prompts

Fail to initialize durable task scheduler connections when deploying with “+ Create new user-assigned identity”

**Initial Findings**: The failure is happening in `ManagedIdentityAssignStep`, specifically with this call: We should add an activity child for this step so it's easier to locate problems coming from this...

Fail to initialize durable task scheduler connections when deploying with “+ Create new user-assigned identity”

So it looks like this is basically happening anywhere we have that update SDK call, even for completely separate commands. For example, I tried unassigning a managed identity, and the...

Fail to initialize durable task scheduler connections when deploying with “+ Create new user-assigned identity”

I'll open a separate issue in a bit for this as it's a wider issue for certain advanced projects

Fail to initialize durable task scheduler connections when deploying with “+ Create new user-assigned identity”

Related: https://github.com/microsoft/vscode-azurefunctions/issues/4859

Ask and give account appropriate privileges to be able to see the DTS dashboard right away

Until we have the full time/resources to devote to implementing this, it might be worth providing an interim note to the user that they need to manually set this up...

An error occurs when canceling C# durable project debugging via prompt dialog

Ahh, this is because the pre-debug validation logic for each connection setting is separate from the main flow; so canceling still allows the rest of the validation to go through......