Added Capability and Readme instructions for manual deployment of service #1

.envrc.template

@@ -30,3 +30,14 @@ export ENTITLEMENT_MEMBER_NAME_INVALID=
 export ENTITLEMENT_MEMBER_NAME_VALID=
 export ENTITLEMENT_GROUP_NAME_VALID=
 
+
+##
+# Needed to manually deploy a service
+##
+
+export AZURE_TENANT_ID=
+export AZURE_CLIENT_ID=
+export AZURE_CLIENT_SECRET=
+export AZURE_RESOURCE_GROUP=
+export AZURE_APPSERVICE_PLAN=
+export AZURE_APPSERVICE_NAME=

.mvn/community-maven.settings.xml

 <settings>
-	<profiles>
-		<profile>
-			<!-- This profile uses the CI-Token to authenticate with the server, and is the default case -->
-			<id>GitLab-Authenticate-With-Job-Token</id>
-			<activation>
-				<activeByDefault>true</activeByDefault>
-			</activation>
-			<properties>
-				<gitlab-server>community-maven-via-job-token</gitlab-server>
-			</properties>
-		</profile>
+  <profiles>
+    <profile>
+      <!-- This profile uses the CI-Token to authenticate with the server, and is the default case -->
+      <id>GitLab-Authenticate-With-Job-Token</id>
+      <activation>
+        <activeByDefault>true</activeByDefault>
+      </activation>
+      <properties>
+        <gitlab-server>community-maven-via-job-token</gitlab-server>
+      </properties>
+    </profile>
 
-		<profile>
-			<!-- This profile uses a personal token to authenticate, which is useful for local or manual runs. The
+    <profile>
+      <!-- This profile uses a personal token to authenticate, which is useful for local or manual runs. The
 			     presence of the COMMUNITY_MAVEN_TOKEN variable triggers this and overrides the CI Token
 			     based authentication -->
-			<id>GitLab-Authenticate-With-Private-Token</id>
-			<activation>
-			<property>
-				<name>env.COMMUNITY_MAVEN_TOKEN</name>
-			</property>
-			</activation>
-			<properties>
-				<gitlab-server>community-maven-via-private-token</gitlab-server>
-			</properties>
-		</profile>
-	</profiles>
+      <id>GitLab-Authenticate-With-Private-Token</id>
+      <activation>
+        <property>
+          <name>env.COMMUNITY_MAVEN_TOKEN</name>
+        </property>
+      </activation>
+      <properties>
+        <gitlab-server>community-maven-via-private-token</gitlab-server>
+      </properties>
+    </profile>
+  </profiles>
 
-	<servers>
-		<server>
-			<id>community-maven-via-job-token</id>
-			<configuration>
-				<httpHeaders>
-					<property>
-						<name>Job-Token</name>
-						<value>${env.CI_JOB_TOKEN}</value>
-					</property>
-				</httpHeaders>
-			</configuration>
-		</server>
+  <servers>
+    <server>
+      <id>community-maven-via-job-token</id>
+      <configuration>
+        <httpHeaders>
+          <property>
+            <name>Job-Token</name>
+            <value>${env.CI_JOB_TOKEN}</value>
+          </property>
+        </httpHeaders>
+      </configuration>
+    </server>
 
-		<server>
-			<id>community-maven-via-private-token</id>
-			<configuration>
-				<httpHeaders>
-					<property>
-						<name>Private-Token</name>
-						<value>${env.COMMUNITY_MAVEN_TOKEN}</value>
-					</property>
-				</httpHeaders>
-			</configuration>
-		</server>
-	</servers>
+    <server>
+      <id>community-maven-via-private-token</id>
+      <configuration>
+        <httpHeaders>
+          <property>
+            <name>Private-Token</name>
+            <value>${env.COMMUNITY_MAVEN_TOKEN}</value>
+          </property>
+        </httpHeaders>
+      </configuration>
+    </server>
+
+    <server>
+      <id>azure-auth</id>
+      <configuration>
+        <tenant>${env.AZURE_TENANT_ID}</tenant>
+        <client>${env.AZURE_CLIENT_ID}</client>
+        <key>${env.AZURE_CLIENT_SECRET}</key>
+        <environment>AZURE</environment>
+      </configuration>
+    </server>
+  </servers>
 </settings>