Optionally skip SND deployment (#312)

VERSION

@@ -1 +1 @@
-v-9.54.0
+v-9.55.0

vars/deployToCluster.groovy

@@ -3,11 +3,13 @@ void call(Map config=[:], Closure body={}) {
 
   node {
     try {
-      stage('Deploy Database') {
-        hasDatabase = database.runRemoteMigrations(config.environment, config.chartName, config.chartVersion)
-      }
-      stage('Deploy Helm chart') {
-        helm.deployRemoteChart(config.environment, config.namespace, config.chartName, config.chartVersion, config.helmChartRepoType)
+      if (config.environment != null) {
+        stage('Deploy Database') {
+          hasDatabase = database.runRemoteMigrations(config.environment, config.chartName, config.chartVersion)
+        }
+        stage('Deploy Helm chart') {
+          helm.deployRemoteChart(config.environment, config.namespace, config.chartName, config.chartVersion, config.helmChartRepoType)
+        }
       }
       stage('Trigger ADO pipelines') {
         ado.triggerPipeline(config.namespace, config.chartName, config.chartVersion, hasDatabase)

vars/deployToCluster.md

@@ -3,10 +3,14 @@
 > The default deploy to cluster build configuration
 
 `deployToCluster` represents a default build configuration for deploying a Helm
-chart to a Kubernetes cluster. Below is an example of how this can be achieved.
+chart to the SND Kubernetes cluster and subsequently triggering the Azure DevOps pipeline to production.
+
+Below is an example of how this can be achieved.
 
 ```
-@Library('defra-library@v-6') _
+@Library('defra-library@v-9') _
 
-deployToCluster environment: 'dev', namespace: 'ffc-demo', chartName: 'ffc-demo-web', chartVersion: '1.0.0', helmChartRepoType: 'acr'
+deployToCluster environment: 'snd', namespace: 'ffc-demo', chartName: 'ffc-demo-web', chartVersion: '1.0.0', helmChartRepoType: 'acr'
 ```
+
+If `environment` is not supplied then the deployment to Kubernetes will be skipped and the pipeline will only trigger the Azure DevOps pipeline.