karlrissland / logic-app-standard-deployment Goto Github PK

Az Role Assignement Create doesn't appear to work with an app registration. Command throws an error and you have to manually add a role assignment.

Looking forward to leveraging AZD, there is a flag that will allow you to deploy parts of an app template. To keep things simple for people new to LogicApps, deploy basic capabilities unless you have chosen advanced features via the AZD Flag.

Create a simple workflow with a few steps that demonstrate customer property tracking. Will need to add Log Analytics to infrastructure deployment and have it wired up to the logic app.

Create and deploy log analytics queries and dashboards to demonstrate how to find and view the custom properties.

This file does a good job of determining if your azure creds are setup correctly. Should also add a test to make sure the GH PAT is setup correctly as it is needed for a few deployment operations.

If you are forking the repository, there are a few things that are needed before workflows will work. This is documented, but it probably takes 30min to 60min to get it configured and tested. It would make things simpler if it were scripted such that, as long as your terminal session has the Azure CLI and the GitHub CLI with the right permissions, you can be up and running in a few minutes

Explain how to get the repo ID and show the new repo variable that needs to be created.

Need to create a repository variable for the repo id and then update the yaml to pull it.

Add functionality to the Call Rest API workflow. It should take an HTTP request, call a rest endpoint, then return results to the initial caller. The rest endpoint uri should be parameterized so it can be variable from dev, to test, to production.

After double clicking the workspace file to open in visual studio, you will eventually be presented with the following toast

Need to configure the workspace so this no longer pops. Clicking yes changes settings that may break the ability to run locally.

Demonstrate mapping json to jason with a liquid map. Show how to upload schemas and maps as a part of the deployment process. Leverage liquid template extensions to help with liquid development.

We have a powershell script to deploy the infrastructure. This is to make it easy for someone to clone the repo and deploy without having to setup a github environment. Need to do the same thing for application deployment. Yes, you can right click deploy from VS code, but having the script would be good for consistency reasons.

Change the workflow_displatch to iterate over environments the same as the infrastructure deployment and the deploy-all deployment

Workflow should leverage a managed azure connector instead of a built-in connector. Need to add the necessary infrastructure as code components to deploy the managed connection and properly parameterize the connection so it is different from dev, to test, to production.

Ideally pick a connector that requires authorization in order to demonstrate how its done.

https://github.com/microsoft/App-Templates is used by the Azure Developer CLI to make it simpler to stand up samples/starting points.

The new GitHub Pat test functionality doesn't test access to variables or secrets in Environments.

Add environment protection rules to require someone to review a deployment to the production environment

We are getting warnings that the version of Node being used needs to be updated.

Build LogicApp Demo
Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/upload-artifact@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

Show how to leverage a reverse proxy tool such as nGrok to send an event grid trigger down to your local development environment.