Parameterized API URLs, App insights, NamedValues environment specific for Creator Tool (#459)

* Azure DevOps Pipeline example

* First commit release pipeline

* Fixed some typos

* Change image size to fit correct on github page.

* Change images size.

* Fixed image size

* Added new images

* Fixed images folder

* Fixed typos

* Fixed typos

* Fixed typo

* Added image files

* Fixed title size

* Added a reference to AzDO Pipeline example

* Updated AzDO-Example.md

* Pick changes from Concurrency changes

* Added Feature to parameterize named values and application insights and backend url using cli inputs

Features added:

1. Application insights parameterized.
2. named values parameterized.
3. API urls parameterized.

* Update Architecture.png

* fix build failure

* Fixed merge issue

* Added Read me file for newly added parameters

Co-authored-by: Osvaldo Daibert <odaibert@microsoft.com>
Co-authored-by: Rupeng Liu <rupliu@microsoft.com>

Author: 3 people

README.md

@@ -43,7 +43,7 @@ We realize there are two challenges for API developers when working with Resourc
 
 * Second, for customers who have already been using API Management, another challenge is how to extract existing configurations into Resource Manager templates. For those customers, We have created another tool called [**Extractor**](./src/APIM_ARMTemplate/README.md#extractor) to help them generate templates by extracting configurations from their exisitng API Management instances.  
 
-Once API developers have finished developing and testing an API, and have generated the API template, they can submit a pull request to merge the changes to the publisher repository. API publishers can validate the pull request and make sure the changes are safe and compliant. For example, they can check if only HTTPS is allowed to communicate with the API. Most of these validations can be automated as a step in the CI/CD pipeline. Once the changes are approved and merged successfully, API publishers can choose to deploy them to the Production instance either on schedule or on demand. The deployment of the templates can be automated using [Github Actions](https://github.com/Azure/apimanagement-devops-samples), [Azure Pipeline](https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops), [PowerShell](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy), [Azure CLI](Azure-cli-example.md) or other tools.
+Once API developers have finished developing and testing an API, and have generated the API template, they can submit a pull request to merge the changes to the publisher repository. API publishers can validate the pull request and make sure the changes are safe and compliant. For example, they can check if only HTTPS is allowed to communicate with the API. Most of these validations can be automated as a step in the CI/CD pipeline. Once the changes are approved and merged successfully, API publishers can choose to deploy them to the Production instance either on schedule or on demand. The deployment of the templates can be automated using [Github Actions](https://github.com/Azure/apimanagement-devops-samples), [Azure Pipeline](https://docs.microsoft.com/en-us/azure/devops/pipelines/?view=azure-devops), [PowerShell](https://docs.microsoft.com/en-us/azure/azure-resource-manager/resource-group-template-deploy), [Azure CLI](Azure-cli-example.md) or other tools. An example using Azure DevOps can be find [here](docs/AzDO-Example.md)
 
 With this approach, the deployment of API changes into API Management instances can be automated and it is easy to promote changes from one environment to another. Since different API development teams will be working on different sets of API templates and files, it prevents interference between different teams.
 

docs/AzDO-Example.md

@@ -0,0 +1,145 @@
+# Continuos Integration and Continuos Deployment using Azure DevOps
+
+The following instructions demonstrate how to deploy the contents of this example repository using Azure DevOps Repos and Azure DevOps Pipelines.
+
+## Pre-reqs
+
+To execute this solution you will need:
+
+- Azure DevOps Account
+- An Azure DevOps Repo configured ([how to configure an Azure DevOps Repo](https://docs.microsoft.com/en-us/azure/devops/repos/get-started/sign-up-invite-teammates?view=azure-devops))
+- Three API Management deployed (DEV, QA and PROD) ([how to deploy a Create a new Azure API Management service instance](https://docs.microsoft.com/en-us/azure/api-management/get-started-create-service-instance))
+- Some API(s) on your API Management ([Add an API manually](https://docs.microsoft.com/en-us/azure/api-management/add-api-manually))
+
+## Architecture
+
+![](images/Architecture.png)
+
+This is one example of how to use Azure DevOps Repo and Azure DevOps Pipelines to enable a Continuous Integration and Continuous Deployment (CI/CD) for API\'s on an Azure API Management Service. There're other ways to do this, but this is a \"Keep it Simple\" to help you start.(Planning to have another version using Github and Github Actions soon).
+
+This is our Development API management. In general, developers will create their API\'s in one instance of APIM to test it.
+
+Create your API's on API Management Development environment. ([How to create API's on API Management](https://docs.microsoft.com/en-us/azure/api-management/import-and-publish))
+
+![](images/apim-dev.png)
+
+## APIM DevOps Toolkit
+
+**Running the Extractor**
+
+After a developer creates and tests APIs in API management, it is time to extract those APIs using this DevOps Resource Kit.
+
+Below are the steps to run the extractor from source code:
+
+- Clone this repository and navigate to {path\_to\_folder}/src/APIM\_ARMTemplate/apimtemplate
+- Restore its packages using
+
+``` 
+dotnet restore 
+```
+
+- Make sure you have signed in using Azure CLI and have switched to the subscription containing the API Management instance from which the configurations will be extracted.
+
+```
+
+az login
+
+az account set \--subscription \<subscription\_id\>
+
+```
+
+**Extractor Arguments**
+
+You have two choices when specifying your settings:
+
+1\. By using a json file with key-values where the keys matches the table below. Use the \`extractorConfig\` argument:
+
+\`extract \--extractorConfig c:/temp/extractSettings.json\`. [See more examples.](#extractorParameterFileExamples)
+
+2\. Pass the arguments on the command line. For instance \`extract \--sourceApimName my-feature-apim \--destinationApimName company-stable-apim \--resourceGroup my-feature-rg \--fileFolder c:\\temp\\apim-extract \--apiName MyFeatureV1Api\`.
+
+For this example, we will only use the option \#2
+
+So, run the application with:
+
+```
+
+dotnet run extract --sourceApimName <DEV-APIM-NAME> --destinationApimName <DESTINATION-APIM-NAME> --resourceGroup <RESOURCE-GROUP-NAME> --fileFolder c:\\temp\\apim-extract.
+
+```
+
+Where:
+
+**DEV-APIM-NAME:** API Management where you created your API
+
+**DESTINATION-APIM-NAME:** It\'s just a convention to set the DESTINATION-API-NAME in front of the generated files.
+
+**RESOURCE-GROUP-NAME:** Resource group where the DEV-APIM-NAME is hosted.
+
+***For more information on how to run the application and parameters, [go to this page](https://github.com/Azure/azure-api-management-devops-resource-kit/blob/master/src/APIM_ARMTemplate/README.md#extractor).***
+
+After executing the command above, you will see something similar to this:
+
+![A screenshot of text Description automatically
+generated](images/extractor.png)
+
+Then you see the json files extracted:
+
+![A close up of text on a white background Description automatically
+generated](images/extracted-files.png)
+
+Now, push them to your Azure DevOps Repo
+
+```
+git push
+```
+
+# Build Pipeline
+
+We will use a **Build Pipeline** to pull the extracted files from a repo and put it on Azure DevOps Artefacts Folder. 
+ 
+1 - Add these tasks to your build:
+- Get Sources
+- Copy Publish Artifacts
+
+2 - Configure the fields as show bellow:
+
+![A screenshot of a cell phone Description automatically
+generated](images/build-pipeline1.png)
+
+![A screenshot of a cell phone Description automatically
+generated](images/build-pipeline2.png)
+
+# Release Pipeline
+
+You can use [this](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/?view=azure-devops) document as a reference on how to create a release pipeline.
+
+1 - Add an [**Azure Deployment tasks**](https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/deploy/azure-resource-group-deployment?view=azure-devops) for each file generated by extractor, following the order:
+
+```
+- Products.template.json
+- Tags.template.json
+- namedValues.template.json
+- apis.template.json
+- globalServicePolice.template.json
+```
+
+2 - Set "Override template parameters" field with "-ApimServiceName \<QA-APIM-NAME>\"
+
+3 - Set set [Deployment mode to Incremental](https://docs.microsoft.com/en-us/azure/azure-resource-manager/templates/deployment-tutorial-pipeline#create-a-devops-project)
+
+![](images/release-qa-parameters.png)
+
+When you finish the steps above, you will see something like this:
+
+![](images/deploy-qa.png)
+
+Clone your QA environment and update the **Resource Group** and **ApimServiceName** value on "Override template parameters" field to reflect your "production" APIM.
+
+![](images/release-prod.png)
+
+Now you will see your Release Pipeline like this:
+
+![](images/release-pipeline.png)
+
+By using a combination of manual deployment approvals, gates, and manual intervention within a release pipeline in Azure Pipelines, you can quickly and easily configure a release pipeline with all the control and auditing capabilities you require for your DevOps CI/CD processes. You will find more information on this [link](https://docs.microsoft.com/en-us/azure/devops/pipelines/release/deploy-using-approvals?view=azure-devops).