Open cloud-owen opened 5 years ago
@pankajsn @davidberg Can one of you take a look
@markcowl Hi, what sort of time frame should we expect a fix in?
I have no connection to this. Please remove me.
Hi, any update on this? It was raised 6 months ago? Thanks
I'm experiencing the same problems. The Id I use at least isn't working even though the same Id worked when deploying the integration account resource with arm template. Pattern used => -IntegrationAccountId "/subscriptions/$AzureSubscriptionId/resourceGroups/$ResourceGroupName/providers/Microsoft.Logic/integrationAccounts/$($DeploymentPrefix)integraccInternal"
Adding the correct @daviburg
Has this been fixed? I too am getting the error "set-azurermlogicapp : The integration account id must be provided in the 'integrationAccount' property of the workflow"
Hi @OpsRaven,
The product team has a bug to address this issue.
Hi, any update on this bug?
Thanks
@daviburg, any updates on addressing this Set-AzureRmLogicApp issue?
@pankajsn Can we provide a response, and if this will be fixed, an ETA?
not sure if it helps, but I have the same issue when using Set-AzlogicApp
Set-AzLogicApp : The workflow '/subscriptions/
I ran into this bug. Is there any chance to fix it? Thanks.
@daviburg, @pankajsn, and @refortie,
Is there an update on fixing this bug with Set-AzureRmLogicApp? Also, related to this issue: https://github.com/Azure/azure-powershell/issues/5233
I ran into this issue today. Do we have any tentative timelines for a fix? Thanks
Pankaj and Reid are working on different teams now. Adding dev manager and will check who can work on LA powershell cmdlet at the moment.
Is there any ETA on a fix for this by now? It appears that not only the IntegrationAccount-Id is an issue, but using this function also removes any authorization policy which has been set. Using this to enable/disable a LogicApp either fails due to the integrationAccount-link, or continues but removes the available authorization policies.
@nidhi-pathak Do you have any updates on this issue ?
This is similar to bug #5233.
Description
I'm attempting to update Logic App Parameters using Set-AzLogicApp.
The commandlet works unless there is an integration account configured against the Logic App, then an error is thrown whether the integration account id is provided as a parameter or not.
Script/Steps for Reproduction
or
I can see in the debug output that the integration account is not being set in either case.
btw, I have removed the workflow definition and parameters from the debug output as it contained sensitive info.
Module Version
Environment Data
Name Value
PSVersion 5.1.17134.407 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.17134.407 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1
Debug Output