Friday, October 7, 2022

Azure Logic Apps deployment using Pipelines

The current pipeline deployment example is based on a Standard Logic App.
I have Build and Release Pipeline.


 Build Pipeline

  1. Create a New Pipeline and give it a name.


  2. Specify Source, Team Project, Repository and default Branch.


  3. Specify Agent Job Name and Agent Pool.

  4. Add an Archive Files task to the Agent Job.
    Specify the following:
    Display name
    Root folder in the repository to archive (containing the Logic App code files)
    Archive type as Zip
    The archive filename to create.

    NB: Be sure to deselect the "Prepend root folder" checkbox.

  5. Add a Publish Build Artifacts task to the Agent Job.
    Specify the following:
    Display name
    Artifact name
    Path to Publish and Artifact Publish location should remain as shown below.




    Congrats, you have now setup your Build Pipeline.




    Release Pipeline

  6. Create new release pipeline.





  7. Add new Artifact.
    Select Source type as "Build"
    Specify Project.
    Select Source (From Build Pipeline)
     



  8. Add new Stage, then click on Tasks and select the newly created Stage
  9. Update Stage name.


  10. Select Agent Job. 
    Update Display name, Agent pool and Agent specification.

  11. Add an Azure App Service deploy task to the Agent job.
    Update all fields as shown below:


    NB: Select deployment method - Zip Deploy

  12. The completed stage should look something like this.




  13. The completed release pipeline should look something like this.







    You may now run you build pipeline and thereafter your release pipeline.


















Monday, May 26, 2014

THERE HAS BEEN AN ERROR WHILE LOADING THE FORM. A REQUIRED RESOURCE COULD NOT BE DOWNLOADED. TO TRY TO RESUME THE DOWNLOAD, REFRESH THE PAGE _ INFOPATH

I found this to be a strange permissions issue.
After going through loads of forums and blogs with people having the same or similar issues.
I tried all the recommended solutions but none of it worked for me.

The only time I did not receive this issue was when I logged into IE with the Admin User.
But this solution was not going to work for everyone.

As a solution / workaround I had to configure IIS,

  • the application pool identity being the Admin User
  • Update the Basic setting of the site to use "Application user (pass-through authentication)" as the Path Credentials
Steps:
  1. Open IIS
  2. Click on Application pools
  3. Right click on the application pool and select "Advanced Setting".

  4. Then select Identity.
  5. Select "Custom account" and set it to the Admin user.
  6. Select Ok.
  7. Update the Basic setting of the site. Select the site.
  8. Click "Basic Settings".
  9. Click "Connect as..."
  10. Select "Application user (pass-through authentication)"