This demo was derived from several best practices and guidelines on API Management deployment process, Git branching/merging strategy and release automation.

• Azure API Management DevOps Resource Kit
• Trunk Based Development
• Release Flow: Microsoft's Branching Strategy

1. Clone this repo locally
2. Clone the APIM DevOps Resource Kit locally as well
3. Checkout a new topic branch called /users/[yourname]/[changesetname]
4. Modify the .env file to to the full path of the /src/APIM_ARMTemplate/apimtemplate folder of the DevOps Kit repo
5. Modify the .env file to include your dev and production instances of APIM and the corresponding Resource Group (this assumes they are both in 1 RG)
6. Run the following command from a bash window: export $(cat .env) to import the environment variables

1. Make an API or policy change to the Dev instance of APIM
2. Checkout a new topic branch called /users/[yourname]/[changesetname]
3. Run the following command from a bash window: bash ./extractConfig.sh
4. The [prodinstancename]-apis-template.json file should be updated with the included changes
5. Commit and push your changes to a new remote branch
6. Submit a Pull Request to merge your changes to master
7. Have PR approved and merged (delete topic branch)
8. Repeat with additional changes (if necessary)
9. When ready to deploy to Production, create a new branch called /releases/[releasename] from master
10. This will automatically trigger the release process