Standard Logic app having service bus Queue does not auto work after deployment from git actions

Question

Standard Logic app having service bus Queue does not auto work after deployment from git actions

Anagh Bhatt 21

Hi
I have deployed Standard logic app many times having service bus queue as trigger . It gets deployed successfully many times. Queue name can be seen in drop down list after deployment but cannot auto start picking messages.
When manually i provide connection string it starts working.
Appreciate if any help is provided on this issue,

Regards
Anagh

MayankBargali-MSFT 70,936 Reputation points Moderator

2022-12-16T05:10:43.357+00:00

@Anagh Bhatt Thanks for reaching out. Please share more details how you are creating the standard logic app and service bus queue trigger workflow. Please share more details in case if you are using ARM or bicep template for the deployment.
Anagh Bhatt 21 Reputation points

2022-12-16T05:18:03.103+00:00

Hi Mayank
Thanks for reply.
with Arm Templates i have created the standard Logic app deployed via git actions. It deployed perfectly.

Then with another git action i am adding workflows.

Here is the connection .json file

{
"serviceProviderConnections": {
"serviceBus": {
"parameterValues": {
"connectionString": "@parameters('connectionStringqas')"
},
"serviceProvider": {
"id": "/serviceProviders/serviceBus"
},
"displayName": "sbconqas"
}
},
"managedApiConnections": {}
}
Parameter file
{
"connectionStringqas": {
"type": "String",
"value": "Endpoint=sb://test1bc.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=6gdbbdbbbbdbdbbdb="
}

}

Anagh Bhatt 21

Here is yml file to deploy logic app standard workflow:

name: release-pipeline
on:
push:

branches: [ main ]

workflow_dispatch:
jobs:
Build-and-DeployQA:

runs-on: windows-latest  
environment: 'Test'  
steps:  
- name: 'Checkout GitHub Action'  
  uses: actions/checkout@master  

- name: Login to Azure  
  uses: azure/login@v1  
  with:  
    creds: ${{secrets.AZURE_CREDENTIALS_TEST}}  
    enable-AzPSSession: true   

- name: Get publish Profile  
  id: fncapp1  
  uses: azure/powershell@v1  
  with:  
    inlineScript: |  
      $profile = Get-AzWebAppPublishingProfile `  
          -ResourceGroupName ${{secrets.RG_QA}} `  
          -Name ${{secrets.LA_NAME_QA}}  
      $profile = $profile.Replace("`r", "").Replace("`n", "")  
      Write-Output "::set-output name=profile::$profile"  
    azPSVersion: latest  
      
- name: Create project folder  
  run: |  
   mkdir output  
    cp 'logic-abcd/host.json' 'output/'  
    #cp 'proxies.json' 'output/'  
    cp 'logic-abcd/parameters.json' 'output/'  
    cp 'logic-abcd/connections.json' 'output/'  
    cp 'logic-abcd/local.settings.json' 'output/'  
    cp -r 'logic-abcd/logic-abcd' 'output/'  
    
  Due to character restriction only main logic is shared

1 answer

Your answer

MayankBargali-MSFT 70,936 Reputation points Moderator

2022-12-16T05:10:43.357+00:00

@Anagh Bhatt Thanks for reaching out. Please share more details how you are creating the standard logic app and service bus queue trigger workflow. Please share more details in case if you are using ARM or bicep template for the deployment.
Anagh Bhatt 21 Reputation points

2022-12-16T05:18:03.103+00:00

Hi Mayank
Thanks for reply.
with Arm Templates i have created the standard Logic app deployed via git actions. It deployed perfectly.

Then with another git action i am adding workflows.

Here is the connection .json file

{
"serviceProviderConnections": {
"serviceBus": {
"parameterValues": {
"connectionString": "@parameters('connectionStringqas')"
},
"serviceProvider": {
"id": "/serviceProviders/serviceBus"
},
"displayName": "sbconqas"
}
},
"managedApiConnections": {}
}
Parameter file
{
"connectionStringqas": {
"type": "String",
"value": "Endpoint=sb://test1bc.servicebus.windows.net/;SharedAccessKeyName=RootManageSharedAccessKey;SharedAccessKey=6gdbbdbbbbdbdbbdb="
}

}
Anagh Bhatt 21 Reputation points

2022-12-16T05:21:54.2+00:00

Here is yml file to deploy logic app standard workflow:

name: release-pipeline
on:
push:

branches: [ main ]

workflow_dispatch:
jobs:
Build-and-DeployQA:

runs-on: windows-latest environment: 'Test' steps: - name: 'Checkout GitHub Action' uses: actions/checkout@master - name: Login to Azure uses: azure/login@v1 with: creds: ${{secrets.AZURE_CREDENTIALS_TEST}} enable-AzPSSession: true - name: Get publish Profile id: fncapp1 uses: azure/powershell@v1 with: inlineScript: | $profile = Get-AzWebAppPublishingProfile ` -ResourceGroupName ${{secrets.RG_QA}} ` -Name ${{secrets.LA_NAME_QA}} $profile = $profile.Replace("`r", "").Replace("`n", "") Write-Output "::set-output name=profile::$profile" azPSVersion: latest - name: Create project folder run: | mkdir output cp 'logic-abcd/host.json' 'output/' #cp 'proxies.json' 'output/' cp 'logic-abcd/parameters.json' 'output/' cp 'logic-abcd/connections.json' 'output/' cp 'logic-abcd/local.settings.json' 'output/' cp -r 'logic-abcd/logic-abcd' 'output/' Due to character restriction only main logic is shared

Answer 1

@Anagh Bhatt Posting as Answer due to character limit. Are you using Azure or In-built service bus trigger? When you create the workflow there would be workflow.json file and it will define your workflow and another i.e. connection.json that you have shared will have the connection details for your standard logic app.

workflow.json

{  
    "definition": {  
        "$schema": "https://schema.management.azure.com/providers/Microsoft.Logic/schemas/2016-06-01/workflowdefinition.json#",  
        "actions": {},  
        "triggers": {  
            "When_a_message_is_received_in_a_queue_(peek-lock)": {  
                "type": "ApiConnection",  
                "inputs": {  
                    "host": {  
                        "connection": {  
                            "referenceName": "servicebus"  
                        }  
                    },  
                    "method": "get",  
                    "path": "/@{encodeURIComponent(encodeURIComponent('cxtest'))}/messages/head/peek",  
                    "queries": {  
                        "queueType": "Main",  
                        "sessionId": "None"  
                    }  
                },  
                "recurrence": {  
                    "frequency": "Minute",  
                    "interval": 15  
                }  
            }  
        },  
        "contentVersion": "1.0.0.0",  
        "outputs": {}  
    },  
    "kind": "Stateful"  
}

connection.json

{  
  "managedApiConnections": {  
    "servicebus": {  
      "api": {  
        "id": "/subscriptions/5a975eab-234f-40cb-aa31-1c4c0344477c/providers/Microsoft.Web/locations/northcentralus/managedApis/servicebus"  
      },  
      "connection": {  
        "id": "/subscriptions/subid/resourceGroups/resourcegroup/providers/Microsoft.Web/connections/servicebus"  
      },  
      "connectionRuntimeUrl": "https://dc7081be1cd1508c.17.common.logic-northcentralus.azure-apihub.net/apim/servicebus/guidid/",  
      "authentication": {  
        "type": "Raw",  
        "scheme": "Key",  
        "parameter": "@appsetting('servicebus-connectionKey')"  
      }  
    }  
  }  
}

To learn more about the code structure and creating standard workflow using VS code you can refer to this document.

Anagh Bhatt 21 Reputation points

2022-12-16T05:58:47.957+00:00

Hi Mayank
I have used In-built connector in Logic app as Service bus trigger.
Let me try with Azure Connector as trigger
Regards
Anagh

Share via

Standard Logic app having service bus Queue does not auto work after deployment from git actions

1 answer

Your answer