A series of sessions with focus on how to set up a Build & Release setup for Common integration parts with VSTS.
In these sessions all will be made hands on and focus will be on understanding the quirks and common tasks.
For API Management we will Create API’s, check in the options we have to extract the code. Create a Build and Release setup inside VSTS to move/promote the API to next step/environment in the chain.
Azure Integration DTAP Series, How to go from Development to Production – Part 1 API Management
1. Azure Integration DTAP Series, How to go
from Development to Production – Part 1
API Management
Mattias Lögdberg https://se.linkedin.com/in/logdberg
2. • Azure Integration DTAP Series,
How to go from Development to Production
Part 1 API Management
Mattias Lögdberg
4. Agenda
• Part 1 of 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
10. Copy Paste, Swager import/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 and Deploy 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
21. Lessons learned
• Full API 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