[Do not merge] Azure spring starter demo sample

.scripts/setup-env-variables-azure-template.sh

@@ -3,27 +3,63 @@
 # ==== Resource Group ====
 export SUBSCRIPTION=subscription-id # customize this
 export RESOURCE_GROUP=resource-group-name # customize this
-export REGION=westus2
-
-# ==== Service and App Instances ====
-export SPRING_CLOUD_SERVICE=azure-spring-cloud-name # customize this
-export API_GATEWAY=api-gateway
-export ADMIN_SERVER=admin-server
-export CUSTOMERS_SERVICE=customers-service
-export VETS_SERVICE=vets-service
-export VISITS_SERVICE=visits-service
-
-# ==== JARS ====
-export API_GATEWAY_JAR=spring-petclinic-api-gateway/target/spring-petclinic-api-gateway-2.2.1.jar
-export ADMIN_SERVER_JAR=spring-petclinic-admin-server/target/spring-petclinic-admin-server-2.2.1.jar
-export CUSTOMERS_SERVICE_JAR=spring-petclinic-customers-service/target/spring-petclinic-customers-service-2.2.1.jar
-export VETS_SERVICE_JAR=spring-petclinic-vets-service/target/spring-petclinic-vets-service-2.2.1.jar
-export VISITS_SERVICE_JAR=spring-petclinic-visits-service/target/spring-petclinic-visits-service-2.2.1.jar
-
-# ==== MYSQL INFO ====
-export MYSQL_SERVER_NAME=mysql-servername # customize this
-export MYSQL_SERVER_FULL_NAME=${MYSQL_SERVER_NAME}.mysql.database.azure.com
-export MYSQL_SERVER_ADMIN_NAME=admin-name # customize this
-export MYSQL_SERVER_ADMIN_LOGIN_NAME=${MYSQL_SERVER_ADMIN_NAME}\@${MYSQL_SERVER_NAME}
-export MYSQL_SERVER_ADMIN_PASSWORD=SuperS3cr3t # customize this
-export MYSQL_DATABASE_NAME=petclinic
+export LOCATION=SouthCentralUS  #customize this
+export COSMOSDB_NAME=mycosmosdbaccname  # customize this
+export REDIS_NAME=myredisname #customize this
+export KEYVAULT_NAME=myend2endkv #customize this
+export APP_NAME_FOR_KEYVAULT=myappforkeyvault #customize this
+
+# ==== Create ResouceGroup ====
+echo "Creating ResouceGroup, it may take a few minutes"
+az group create --name ${RESOURCE_GROUP} \
+        --location ${LOCATION}
+
+# ==== Create CosmosDB Account ====
+echo "Creating CosmosDB Account, it may take a few minutes"
+az cosmosdb create --name $COSMOSDB_NAME --resource-group $RESOURCE_GROUP
+COSMOS_KEYS=$(az cosmosdb keys list --name $COSMOSDB_NAME --resource-group $RESOURCE_GROUP --type keys)
+COSMOS_PRIMARY_KEY=$(echo $COSMOS_KEYS | jq -r .primaryMasterKey)
+COSMOS_SECONDARY_KEY=$(echo $COSMOS_KEYS | jq -r .secondaryMasterKey)
+COSMOSDB_URI=$(az cosmosdb  show --name $COSMOSDB_NAME --resource-group $RESOURCE_GROUP | jq -r .documentEndpoint)
+
+# ==== Create Redis Cache Account ====
+echo "Creating Redis Cache Account, it may take a few minutes"
+az redis create --name $REDIS_NAME  --resource-group $RESOURCE_GROUP --sku Basic --vm-size c0 --location $LOCATION
+REDIS_HOSTNAME=$(az redis show --name $REDIS_NAME --resource-group $RESOURCE_GROUP | jq -r .hostName)
+REDIS_PASSWORD=$(az redis list-keys --name $REDIS_NAME --resource-group $RESOURCE_GROUP | jq -r .primaryKey)
+
+# ==== Create KeyVault Account ====
+echo "Creating KeyVault Account, it may take a few minutes"
+az keyvault create --location $LOCATION --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP
+
+SERVICE_PRINCIPAL=$(az ad sp create-for-rbac --name ${APP_NAME_FOR_KEYVAULT} --role Contributor)
+
+AZURE_KEYVAULT_URI=$(az keyvault show --name $KEYVAULT_NAME --resource-group $RESOURCE_GROUP | jq -r .properties | jq -r .vaultUri)
+AZURE_KEYVAULT_CLIENTID=$(echo $SERVICE_PRINCIPAL | jq -r .appId)
+AZURE_KEYVAULT_TENANTID=$(echo $SERVICE_PRINCIPAL | jq -r .tenant)
+AZURE_KEYVAULT_CLIENTKEY=$(echo $SERVICE_PRINCIPAL | jq -r .password)
+
+# set keyvault policy
+az keyvault set-policy -n $KEYVAULT_NAME --key-permissions get list \
+ --certificate-permissions get list \
+ --secret-permissions get list \
+ --resource-group $RESOURCE_GROUP \
+ --spn $AZURE_KEYVAULT_CLIENTID
+
+# ==== add keys to keyvault ====
+echo "add keys to keyvault"
+az keyvault secret set --vault-name $KEYVAULT_NAME --name cosmosdburi --value $COSMOSDB_URI
+az keyvault secret set --vault-name $KEYVAULT_NAME --name cosmosdbkey --value $COSMOS_PRIMARY_KEY
+az keyvault secret set --vault-name $KEYVAULT_NAME --name cosmosdbsecondarykey --value $COSMOS_SECONDARY_KEY
+az keyvault secret set --vault-name $KEYVAULT_NAME --name redisuri --value $REDIS_HOSTNAME
+az keyvault secret set --vault-name $KEYVAULT_NAME --name redispassword --value $REDIS_PASSWORD
+
+
+# ==== Create Kevvault environment file for Docker containers ====
+cat > keyvault.env << EOF
+AZURE_KEYVAULT_URI=$AZURE_KEYVAULT_URI
+AZURE_KEYVAULT_CLIENTID=$AZURE_KEYVAULT_CLIENTID
+AZURE_KEYVAULT_TENANTID=$AZURE_KEYVAULT_TENANTID
+AZURE_KEYVAULT_CLIENTKEY=$AZURE_KEYVAULT_CLIENTKEY
+EOF
+echo "environment configuration complete"

README-petclinic.md

@@ -47,47 +47,14 @@ You can then access petclinic here: http://localhost:8080/
 
 ![Spring Petclinic Microservices screenshot](docs/application-screenshot.png)
 
+**Architecture diagram of the Spring Petclinic Microservices with CosmosDB**
 
-**Architecture diagram of the Spring Petclinic Microservices**
-
-![Spring Petclinic Microservices architecture](docs/microservices-architecture-diagram.jpg)
-
+![Spring Petclinic Microservices architecture](docs/microservices-architecture-diagram-cosmosdb.jpg)
 
 ## In case you find a bug/suggested improvement for Spring Petclinic Microservices
 
 Our issue tracker is available here: https://github.com/spring-petclinic/spring-petclinic-microservices/issues
 
-## Database configuration
-
-In its default configuration, Petclinic uses an in-memory database (HSQLDB) which gets populated at startup with data.
-A similar setup is provided for MySql in case a persistent database configuration is needed.
-Dependency for Connector/J, the MySQL JDBC driver is already included in the `pom.xml` files.
-
-### Start a MySql database
-
-You may start a MySql database with docker:
-
-```
-docker run -e MYSQL_ROOT_PASSWORD=petclinic -e MYSQL_DATABASE=petclinic -p 3306:3306 mysql:5.7.8
-```
-or download and install the MySQL database (e.g., MySQL Community Server 5.7 GA), which can be found here: https://dev.mysql.com/downloads/
-
-### Use the Spring 'mysql' profile
-
-To use a MySQL database, you have to start 3 microservices (`visits-service`, `customers-service` and `vets-services`)
-with the `mysql` Spring profile. Add the `--spring.profiles.active=mysql` as programm argument.
-
-By default, at startup, database schema will be created and data will be populated.
-You may also manually create the PetClinic database and data by executing the `"db/mysql/{schema,data}.sql"` scripts of each 3 microservices. 
-In the `application.yml` of the [Configuration repository], set the `initialization-mode` to `never`.
-
-If you are running the microservices with Docker, you have to add the `mysql` profile into the (Dockerfile)[docker/Dockerfile]:
-```
-ENV SPRING_PROFILES_ACTIVE docker,mysql
-```
-In the `mysql section` of the `application.yml` from the [Configuration repository], you have to change 
-the host and port of your MySQL JDBC connection string. 
-
 ## Custom metrics monitoring
 
 Grafana and Prometheus are included in the `docker-compose.yml` configuration, and the public facing applications