-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting issue during workflow deployment #6254
Comments
Can you add some repro steps, your workflow json and any other information which will help us debug this better please? |
We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed. |
Hi @ashriva1987 this might be related to #6149. There is a private vsix at the last comment, is there any chance you can download, install it and give it a try? |
We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed. |
Hi Team, I am using bicep template for creating logic apps and also for creating standard logic app workflow. I have installed the extension in VS code for seeing the designer view. but its not loading. Thanks |
Hi @ashriva1987 thanks for raising this issue. Could you please share the whole structure of the worklow that was created using your bicep template? |
{ |
I am getting below error while try to open logic app workflow in designer mode. Azure Functions Core Tools Value cannot be null. (Parameter 'provider') |
Hi @ashriva1987 so the error above usually comes when opening the designer. I know you stated that the issue came up when deploying it, but is this the case for when opening the designer?
|
We requested more information to triage this issue. If the issue goes more than 7 days with no more information it'll be automatically closed. |
I tested with a private fix from @ccastrotrejo and now I can able to deploy the logic app without the above issue. However, facing some unseen issues where the logic app workflow doesn't show the essential details like workflow status, workflow URL, and so on. Not sure whether the issue is with the logic app tool or an issue in the Azure portal that doesn't show the details. With this, We aren't able to manually run the workflow which was developed and deployed from the Logic App tool from VSCode whereas I can able to see all the essential details of the workflow which was created from the Azure portal. |
Does this occur consistently?
Repro steps:
1.
2.
Action: azureLogicAppsStandard.deploy
Error type: AggregateAuthenticationError
Error Message: EnvironmentCredential is unavailable. No underlying credential could be used. To troubleshoot, visit redacted:url
Version: 4.107.4
OS: win32
OS Release: 10.0.22631
Product: Visual Studio Code
Product Version: 1.96.0
Language: en
Call Stack
¨NBSP;The text was updated successfully, but these errors were encountered: