Downloaded 19 times
Uploaded byBizTalk360
Azure Integration DTAP Series, How to go from Development to Production – Part 1 API Management
This document is the first part of a series by Mattias Lögdberg, detailing the process of moving from development to production in Azure, specifically focusing on API management. It covers deployment flows, various deployment methods, and highlights lessons learned regarding best practices and challenges faced in using tools like VSTS, Git, and ARM templates. The document emphasizes the importance of careful management of resources and deployment methods to avoid issues in production environments.
More Related Content
Similar to Azure Integration DTAP Series, How to go from Development to Production – Part 1 API Management
Azure Integration DTAP Series, How to go from Development to Production – Part 1 API Management
- 1. Azure Integration DTAPSeries, How to go from Development to Production – Part 1 API Management Mattias Lögdberg https://se.linkedin.com/in/logdberg
- 2. • Azure IntegrationDTAP Series, How to go from Development to Production Part 1 API Management Mattias Lögdberg
- 3. Mattias Lögdberg Solution Architect AzureSpecialist Azure Advisor & Insider http://mlogdberg.com MLogdberg MLogdberg https://se.linkedin.com/in/logdberg
- 4. Agenda • Part 1of a set of 3 series covering build and release processes with VSTS • API Management • Azure Functions • Logic Apps • Intro • Hands on setup in VSTS • Lessons learned, tips and trix • Questions
- 5.
- 6. Developing with AzureAPI Management
- 7.
- 8.
- 9. Deployment Options Copy Paste,Swagger Export/Import Powershell / REST API GIT ARM Template
- 10. Copy Paste, Swagerimport/export Pros: • Easy to get started Cons: • How to make sure all resources are update • Policies on Multiple levels • Oauth • Backends • Reliable deployments? Doing the same mistakes over and over again
- 11. PowerShell / REST Pros: •All functions needed • Flexibility Cons: • More time spent developing the deployment process • What if we add something new? • Does the scripts/flows takes this into consideration?
- 12. GIT Pros: • Release andDeploy in separate steps • History on all changes • Contains almost all resources • Missing Named Values (Properties) Cons: • File based • Need powershell to edit URL’s etc • Regenerate Passwor every 30 days*
- 13. ARM Templates Pros: • ”Standard”Azure deployment • Contains all resources • Out of box support for Key Vault during deployments • Possible to find other Azure Resources for auto generating keys etc Cons: • Preview (export not 100% correct) • Need powershell to ”fix” the template
- 14.
- 15.
- 16.
- 17. Recap GIT Setup Build VSTS Releases Test QA Prod Filter:INT001* Test QA Prod Dev
- 18.
- 19.
- 20.
- 21. Lessons learned • FullAPI Management deployments is dangerous • Make sure to only deploy the API’s that are suppose to be changed • GIT and working with Groups is messy cross instances • Easier to maintain manually • Generate new key every 30 day for GIT is messing up build and release history • Don’t combine deployment methods with GIT • Potential small changes as Logic App trigger URL’ can be painfull. • ARM deployments support KeyVault
- 22.
- 23. Links • http://blog.ibiz-solutions.se/integration/API-Management-DTAP- Pipeline-VSTS/ • http://blog.ibiz-solutions.se/integration/understanding-api- management-source-code/ •http://mlogdberg.com/apimanagement/arm-template-creator • https://www.visualstudio.com/en-us/docs/build/preview/release- definition-editor • https://docs.microsoft.com/en-us/azure/azure-resource- manager/resource-group-template-functions
- 24. Thanks! Mattias Lögdberg, SolutionsArchitect Email: Mattias. Logdberg@ibiz-solutions.se
Editor's Notes
- #11 SOAP services require new import of wsdl Backend resource cannot be edited/created in GUI