@leverege/build-tools 1.10.7 → 1.11.0

package/lib/server/circleate

@@ -183,6 +183,10 @@ jobs:
           name: Run Tests and Generate Code Coverage
           command: npm run coverage
 
+      - run:
+          name: Check if coverage meets at least 70%
+          command: ./node_modules/.bin/nyc check-coverage --branches 70 --functions 70 --lines 70 --statements 70
+
       - run: 
           name: Generate docs
           command: |
@@ -367,6 +371,10 @@ jobs:
           name: Run Tests and Generate Code Coverage
           command: npm run coverage
 
+      - run:
+          name: Check if coverage meets at least 70%
+          command: ./node_modules/.bin/nyc check-coverage --branches 70 --functions 70 --lines 70 --statements 70
+
       - run: 
           name: Generate docs
           command: |

package/lib/server/helmup

@@ -106,6 +106,81 @@ function checkSSDStorageClass(){
   printf "\n*** Attaching PVC to SSD Class ***\n\n"
 }
 
+function installVelero() {
+  ## Set the project id by parsing current context
+  currContext=`kubectl config current-context`
+   
+  IFS='_'
+  read -ra ADDR <<< "$currContext" 
+
+  PROJECT_ID=${ADDR[1]} # project id is the second string split by _
+
+  gcloud config set project $PROJECT_ID
+
+  ## Create a bucket
+  BUCKET="$PROJECT_ID-velero"
+
+  gsutil mb gs://$BUCKET/
+
+  ## Create a service account
+  gcloud iam service-accounts create velero \
+    --display-name "Velero service account"
+
+  SERVICE_ACCOUNT_EMAIL=$(gcloud iam service-accounts list \
+    --filter="displayName:Velero service account" \
+    --format 'value(email)')
+
+  ## Attach roles
+  ROLE_PERMISSIONS=(
+    compute.disks.get
+    compute.disks.create
+    compute.disks.createSnapshot
+    compute.snapshots.get
+    compute.snapshots.create
+    compute.snapshots.useReadOnly
+    compute.snapshots.delete
+    compute.zones.get
+  )
+
+  gcloud iam roles create velero.server \
+    --project $PROJECT_ID \
+    --title "Velero Server" \
+    --permissions "$(IFS=","; echo "${ROLE_PERMISSIONS[*]}")"    
+
+  gcloud projects add-iam-policy-binding $PROJECT_ID \
+    --member serviceAccount:$SERVICE_ACCOUNT_EMAIL \
+    --role projects/$PROJECT_ID/roles/velero.server
+
+  gsutil iam ch serviceAccount:$SERVICE_ACCOUNT_EMAIL:objectAdmin gs://${BUCKET}
+
+  ## Create keys
+  gcloud iam service-accounts keys create credentials-velero \
+    --iam-account $SERVICE_ACCOUNT_EMAIL
+
+  ## Create velero namespace
+  kubectl create ns velero
+
+  ## Create kubernetes secret
+  kubectl create secret generic velero-credentials --namespace velero --from-file cloud=credentials-velero
+
+  ## Install velero
+  helm upgrade --install velero stable/velero \
+    --namespace velero \
+    --set configuration.provider="gcp" \
+    --set configuration.backupStorageLocation.name="gcp" \
+    --set configuration.volumeSnapshotLocation.name="gcp" \
+    --set configuration.backupStorageLocation.bucket="${BUCKET}" \
+    --set credentials.existingSecret="velero-credentials" \
+    --set schedules.timescale.schedule="0 3 * * *" \
+    --set schedules.timescale.template.ttl="720h" \
+    --set schedules.timescale.template.labelSelector.matchLabels.app="postgresql" \
+    --set schedules.timescale.template.snapshotVolumes="true"
+
+  ## Instruct users to move velero keys
+  printf "\n$YELO_WARN MOVE THE SERVICE ACCOUNT TO YOUR KEYS FOLDER"
+  printf "\n$YELO_WARN NO REALLY...MOVE credentials-velero file NOW"
+}
+
 function installKeel() {
   [ ! -d "$LEV_KEYS" ] &&
     keelNeeds "`color c \\$LEV_KEYS` must point to the keys directory for the clusters."
@@ -225,6 +300,10 @@ function doInstall() {
         helm upgrade --install ingress ./ingress
         ;;
 
+      "velero")
+        installVelero # because it's a little more involved
+        ;;
+
       *)
         if [ ! -d $SERVICE ] || [ ! -f $SERVICE/values-local.yaml ];
         then

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "1.10.7",
+  "version": "1.11.0",
   "description": "A package for development build tools.",
   "main": "index.js",
   "scripts": {

package/src/circleate

@@ -183,6 +183,10 @@ jobs:
           name: Run Tests and Generate Code Coverage
           command: npm run coverage
 
+      - run:
+          name: Check if coverage meets at least 70%
+          command: ./node_modules/.bin/nyc check-coverage --branches 70 --functions 70 --lines 70 --statements 70
+
       - run: 
           name: Generate docs
           command: |
@@ -367,6 +371,10 @@ jobs:
           name: Run Tests and Generate Code Coverage
           command: npm run coverage
 
+      - run:
+          name: Check if coverage meets at least 70%
+          command: ./node_modules/.bin/nyc check-coverage --branches 70 --functions 70 --lines 70 --statements 70
+
       - run: 
           name: Generate docs
           command: |

package/src/helmup

@@ -106,6 +106,81 @@ function checkSSDStorageClass(){
   printf "\n*** Attaching PVC to SSD Class ***\n\n"
 }
 
+function installVelero() {
+  ## Set the project id by parsing current context
+  currContext=`kubectl config current-context`
+   
+  IFS='_'
+  read -ra ADDR <<< "$currContext" 
+
+  PROJECT_ID=${ADDR[1]} # project id is the second string split by _
+
+  gcloud config set project $PROJECT_ID
+
+  ## Create a bucket
+  BUCKET="$PROJECT_ID-velero"
+
+  gsutil mb gs://$BUCKET/
+
+  ## Create a service account
+  gcloud iam service-accounts create velero \
+    --display-name "Velero service account"
+
+  SERVICE_ACCOUNT_EMAIL=$(gcloud iam service-accounts list \
+    --filter="displayName:Velero service account" \
+    --format 'value(email)')
+
+  ## Attach roles
+  ROLE_PERMISSIONS=(
+    compute.disks.get
+    compute.disks.create
+    compute.disks.createSnapshot
+    compute.snapshots.get
+    compute.snapshots.create
+    compute.snapshots.useReadOnly
+    compute.snapshots.delete
+    compute.zones.get
+  )
+
+  gcloud iam roles create velero.server \
+    --project $PROJECT_ID \
+    --title "Velero Server" \
+    --permissions "$(IFS=","; echo "${ROLE_PERMISSIONS[*]}")"    
+
+  gcloud projects add-iam-policy-binding $PROJECT_ID \
+    --member serviceAccount:$SERVICE_ACCOUNT_EMAIL \
+    --role projects/$PROJECT_ID/roles/velero.server
+
+  gsutil iam ch serviceAccount:$SERVICE_ACCOUNT_EMAIL:objectAdmin gs://${BUCKET}
+
+  ## Create keys
+  gcloud iam service-accounts keys create credentials-velero \
+    --iam-account $SERVICE_ACCOUNT_EMAIL
+
+  ## Create velero namespace
+  kubectl create ns velero
+
+  ## Create kubernetes secret
+  kubectl create secret generic velero-credentials --namespace velero --from-file cloud=credentials-velero
+
+  ## Install velero
+  helm upgrade --install velero stable/velero \
+    --namespace velero \
+    --set configuration.provider="gcp" \
+    --set configuration.backupStorageLocation.name="gcp" \
+    --set configuration.volumeSnapshotLocation.name="gcp" \
+    --set configuration.backupStorageLocation.bucket="${BUCKET}" \
+    --set credentials.existingSecret="velero-credentials" \
+    --set schedules.timescale.schedule="0 3 * * *" \
+    --set schedules.timescale.template.ttl="720h" \
+    --set schedules.timescale.template.labelSelector.matchLabels.app="postgresql" \
+    --set schedules.timescale.template.snapshotVolumes="true"
+
+  ## Instruct users to move velero keys
+  printf "\n$YELO_WARN MOVE THE SERVICE ACCOUNT TO YOUR KEYS FOLDER"
+  printf "\n$YELO_WARN NO REALLY...MOVE credentials-velero file NOW"
+}
+
 function installKeel() {
   [ ! -d "$LEV_KEYS" ] &&
     keelNeeds "`color c \\$LEV_KEYS` must point to the keys directory for the clusters."
@@ -225,6 +300,10 @@ function doInstall() {
         helm upgrade --install ingress ./ingress
         ;;
 
+      "velero")
+        installVelero # because it's a little more involved
+        ;;
+
       *)
         if [ ! -d $SERVICE ] || [ ! -f $SERVICE/values-local.yaml ];
         then