@leverege/build-tools 2.57.2 → 2.57.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leverege/build-tools",
-  "version": "2.57.2",
+  "version": "2.57.4",
   "description": "A collection of build / support tools for Leverege developers",
   "main": "index.js",
   "repository": {

package/src/circleate.sh

@@ -87,7 +87,7 @@ jobs:
           at: ~/project
       - run:
           name: Check for vulnerabilities
-          command: npm audit --production --audit-level=moderate
+          command: npm audit --omit=dev --audit-level=moderate
 
   license-check:
     docker:
@@ -303,7 +303,7 @@ jobs:
           at: ~/project
       - run:
           name: Check for vulnerabilities
-          command: npm audit --production --audit-level=moderate
+          command: npm audit --omit=dev --audit-level=moderate
 
   license-check:
     docker:

package/src/helm-charts/api-server/values-local.yaml

@@ -5,7 +5,7 @@
 #     - node tools/UpdateESMappingV2.js
 #
 image:
-  tag: # v5.16.0
+  tag: # v5.17.5
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/authz-server/values-local.yaml

@@ -4,7 +4,7 @@
 #     - npm run sequelizeRunMigrations
 #
 image:
-  tag: # v2.2.0
+  tag: # v2.4.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/db-curator/values-local.yaml

@@ -1,5 +1,5 @@
 image:
-  tag: # v4.3.0
+  tag: # v4.4.2
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/emailer/values-local.yaml

@@ -1,5 +1,5 @@
 image:
-  tag: # v3.5.1
+  tag: # v3.7.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/fota-server/values-local.yaml

@@ -1,5 +1,5 @@
 image:
-  tag: # v1.2.2
+  tag: # v2.1.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'
@@ -9,3 +9,6 @@ config:
 
   # CNPG override
 # SQL_HOST: "cnpg-db-psql-stack-rw.cnpg-operands" # vs postgres-postgresql
+
+serviceMonitor:
+  enabled: false

package/src/helm-charts/message-processor/values-local.yaml

@@ -1,5 +1,8 @@
 image:
-  tag: # v4.0.0
+  tag: # v4.2.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'
+
+serviceMonitor:
+  enabled: false

package/src/helm-charts/messenger/values-local.yaml

@@ -1,5 +1,5 @@
 image:
- tag: # v2.11.1
+ tag: # v2.14.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/prom-operator/rules/cnpg-rules.yaml

@@ -0,0 +1,125 @@
+apiVersion: monitoring.coreos.com/v1
+kind: PrometheusRule
+metadata:
+  name: cnpg-default-alerts
+spec:
+  groups:
+  - name: cnpg-default.rules
+    rules:
+    - alert: LongRunningTransaction
+      annotations:
+        description: Pod {{ $labels.pod }} is taking more than 5 minutes (300 seconds) for a query.
+        summary: A query is taking longer than 5 minutes.
+      expr: |-
+        cnpg_backends_max_tx_duration_seconds > 300
+      for: 1m
+      labels:
+        severity: warning
+    - alert: BackendsWaiting
+      annotations:
+        description: Pod {{ $labels.pod  }} has been waiting for longer than 5 minutes
+        summary: If a backend is waiting for longer than 5 minutes
+      expr: |-
+        cnpg_backends_waiting_total > 300
+      for: 1m
+      labels:
+        severity: warning
+    - alert: PGDatabaseXidAge
+      annotations:
+        description: Over 150,000,000 transactions from frozen xid on pod {{ $labels.pod  }}
+        summary: Number of transactions from the frozen XID to the current one
+      expr: |-
+        cnpg_pg_database_xid_age > 300000000
+      for: 1m
+      labels:
+        severity: warning
+    - alert: PGReplication
+      annotations:
+        description: Standby is lagging behind by over 300 seconds (5 minutes)
+        summary: The standby is lagging behind the primary
+      expr: |-
+        cnpg_pg_replication_lag > 300
+      for: 1m
+      labels:
+        severity: warning
+    - alert: LastFailedArchiveTime 
+      annotations:
+        description: Archiving failed for {{ $labels.pod }}
+        summary: Checks the last time archiving failed. Will be < 0 when it has not failed.
+      expr: |-
+        (cnpg_pg_stat_archiver_last_failed_time - cnpg_pg_stat_archiver_last_archived_time) > 1
+      for: 1m
+      labels:
+        severity: warning
+    - alert: DatabaseDeadlockConflicts 
+      annotations:
+        description: There are over 10 deadlock conflicts in {{ $labels.pod }}
+        summary: Checks the number of database conflicts
+      expr: |-
+        cnpg_pg_stat_database_deadlocks > 10
+      for: 1m
+      labels:
+        severity: warning
+    - alert: ReplicaFailingReplication
+      annotations:
+        description: Replica {{ $labels.pod }} is failing to replicate
+        summary: Checks if the replica is failing to replicate
+      expr: |-
+        cnpg_pg_replication_in_recovery > cnpg_pg_replication_is_wal_receiver_up
+      for: 1m
+      labels:
+        severity: warning
+#
+# folding in rules based on non-cnpg postgres metrics
+#
+    - alert: PostgresqlDown
+      expr: cnpg_collector_up == 0
+      for: 0m
+      labels:
+        severity: critical
+      annotations:
+        summary: Postgresql down (instance {{ $labels.instance }})
+        description: "Postgresql instance is down\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"
+
+    - alert: PostgresqlRestarted
+      expr: time() - cnpg_pg_postmaster_start_time < 60
+      for: 0m
+      labels:
+        severity: critical
+      annotations:
+        summary: Postgresql restarted (instance {{ $labels.instance }})
+        description: "Postgresql restarted\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"
+
+    - alert: PostgresqlHighRollbackRate
+      expr: sum by (namespace,datname) ((rate(cnpg_pg_stat_database_xact_rollback{datname!~"template.*|postgres",datid!="0"}[3m])) / ((rate(cnpg_pg_stat_database_xact_rollback{datname!~"template.*|postgres",datid!="0"}[3m])) + (rate(cnpg_pg_stat_database_xact_commit{datname!~"template.*|postgres",datid!="0"}[3m])))) > 0.02
+      for: 0m
+      labels:
+        severity: warning
+      annotations:
+        summary: Postgresql high rollback rate (instance {{ $labels.instance }})
+        description: "Ratio of transactions being aborted compared to committed is > 2 %\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"
+
+#   - alert: PostgresqlCommitRateLow
+#     expr: rate(pg_stat_database_xact_commit[1m]) < 10
+#     for: 2m
+#     labels:
+#       severity: critical
+#     annotations:
+#       summary: Postgresql commit rate low (instance {{ $labels.instance }})
+#       description: "Postgresql seems to be processing very few transactions\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"    - alert: PostgresqlCommitRateLow
+#     expr: rate(cnpg_pg_stat_database_xact_commit[1m]) < 10
+#     for: 2m
+#     labels:
+#       severity: critical
+#     annotations:
+#       summary: Postgresql commit rate low (instance {{ $labels.instance }})
+#       description: "Postgresql seems to be processing very few transactions\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"
+
+#   - alert: PostgresqlUnusedReplicationSlot
+#     expr: cnpg_pg_replication_slots_active == 0
+#     for: 1m
+#     labels:
+#       severity: warning
+#     annotations:
+#       summary: Postgresql unused replication slot (instance {{ $labels.instance }})
+#       description: "Unused Replication Slots\n  VALUE = {{ $value }}\n  LABELS = {{ $labels }}"

package/src/helm-charts/prom-operator/rules/{elasticsearch-rules.yaml.ovh → elasticsearch-rules.yaml}

@@ -17,7 +17,6 @@ spec:
       annotations:
         summary: "Elasticsearch Heap Usage Too High (instance {{ $labels.instance }})"
         description: "The heap usage is over 90% for 5m (currently at {{ $value }}% )"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchHeapUsageWarning
       expr: (elasticsearch_jvm_memory_used_bytes{area="heap"} / elasticsearch_jvm_memory_max_bytes{area="heap"}) * 100 > 80
@@ -27,7 +26,6 @@ spec:
       annotations:
         summary: "Elasticsearch Heap Usage warning (instance {{ $labels.instance }})"
         description: "The heap usage is over 80% for 5m (currently at {{ $value }}% )"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchDiskSpaceLow
       expr: elasticsearch_filesystem_data_available_bytes / elasticsearch_filesystem_data_size_bytes * 100 < 20
@@ -37,7 +35,6 @@ spec:
       annotations:
         summary: "Elasticsearch disk space low (instance {{ $labels.instance }})"
         description: "The disk usage is over 80% (currently at {{ $value }}% )"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchDiskOutOfSpace
       expr: elasticsearch_filesystem_data_available_bytes / elasticsearch_filesystem_data_size_bytes * 100 < 10
@@ -48,7 +45,6 @@ spec:
       annotations:
         summary: "Elasticsearch disk out of space (instance {{ $labels.instance }})"
         description: "The disk usage is over 90% (currently at {{ $value }}% )"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchClusterRed
       expr: elasticsearch_cluster_health_status{color="red"} == 1
@@ -58,7 +54,6 @@ spec:
       annotations:
         summary: "Elasticsearch Cluster Red (instance {{ $labels.instance }})"
         description: "Elastic Cluster is in an unhealthy state"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchClusterYellow
       expr: elasticsearch_cluster_health_status{color="yellow"} == 1
@@ -68,7 +63,6 @@ spec:
       annotations:
         summary: "Elasticsearch Cluster Yellow (instance {{ $labels.instance }})"
         description: "Elastic Cluster is in an unhealthy state"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchRelocationShards
       expr: elasticsearch_cluster_health_relocating_shards > 0
@@ -78,7 +72,6 @@ spec:
       annotations:
         summary: "Elasticsearch relocation shards (instance {{ $labels.instance }})"
         description: "Number of relocation shards for 20 min is {{ $value }}"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchInitializingShards
       expr: elasticsearch_cluster_health_initializing_shards > 0
@@ -88,7 +81,6 @@ spec:
       annotations:
         summary: "Elasticsearch initializing shards (instance {{ $labels.instance }})"
         description: "Number of initializing shards for 10 min is {{ $value }}"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchUnassignedShards
       expr: elasticsearch_cluster_health_unassigned_shards > 0
@@ -98,7 +90,6 @@ spec:
       annotations:
         summary: "Elasticsearch unassigned shards (instance {{ $labels.instance }})"
         description: "Number of unassigned shards for 2 min is {{ $value }}"
-        dashboard: "OVH:<MONITORING>/elasticsearch"
 
     - alert: ElasticsearchPendingTasks
       expr: elasticsearch_cluster_health_number_of_pending_tasks > 0
@@ -108,4 +99,3 @@ spec:
       annotations:
         summary: "Elasticsearch pending tasks (instance {{ $labels.instance }})"
         description: "Number of pending tasks for 10 min is {{ $value }}. Cluster is working slowly."
-        dashboard: "OVH:<MONITORING>/elasticsearch"

package/src/helm-charts/prom-operator/rules/{gcp-rules.yaml.ovh → gcp-rules.yaml}

@@ -25,7 +25,6 @@ spec:
       annotations:
         summary: "High Firebase load detected"
         description: "Firebase load is above 90% (current value is: {{ $value | humanize }}%)"
-        dashboard: "OVH:<MONITORING>/firebase"   
     - alert: PubSubUndeliveredMessages
       expr: sum(stackdriver_pubsub_subscription_pubsub_googleapis_com_subscription_num_undelivered_messages) by (subscription_id) > 1000
       for: 5m 
@@ -35,7 +34,6 @@ spec:
       annotations:
         summary: "High Number of Undelivered Messages on PubSub"
         description: "Undelivered message count on topic {{$labels.subscription_id}} is greater than 1000"
-        dashboard: "OVH:<MONITORING>/stackdriver"
     - alert: PubSubOldUnackedMessages
       expr: stackdriver_pubsub_subscription_pubsub_googleapis_com_subscription_oldest_unacked_message_age > 900
       for: 5m 
@@ -44,4 +42,3 @@ spec:
       annotations:
         summary: "Old messages left unacked on PubSub"
         description: "Messages on {{$labels.subscription_id}} has been unacked for more than 15m"
-        dashboard: "OVH:<MONITORING>/stackdriver"

package/src/helm-charts/prom-operator/rules/{kubernetes-rules.yaml.ovh → kubernetes-rules.yaml}

@@ -58,7 +58,6 @@ spec:
       annotations:
         summary: "Kubernetes PVC Free Space < 10%"
         description: "PVC volume {{ $labels.persistentvolumeclaim }} is almost full - down to {{ $value | humanize }}% available"
-        dashboard: "OVH:<MONITORING>/k8s-pvc/pvc-usage?var-volume={{ $labels.persistentvolumeclaim }}"
 
 #   - alert: KubernetesVolumeFullInFourDays
 #     expr: predict_linear(kubelet_volume_stats_available_bytes[6h], 4 * 24 * 3600) < 0
@@ -68,7 +67,6 @@ spec:
 #     annotations:
 #       summary: "Kubernetes Volume full in four days "
 #       description: "{{ $labels.namespace }}/{{ $labels.persistentvolumeclaim }} is expected to fill up within four days. Currently {{ $value | humanize }}% is available."
-#       dashboard: "OVH:<MONITORING>/pvc"
 
     - alert: KubernetesPersistentvolumeError
       expr: kube_persistentvolume_status_phase{phase=~"Failed|Pending",job="kube-state-metrics"} > 0
@@ -88,7 +86,6 @@ spec:
       annotations:
         summary: "Kubernetes HPA scale capability"
         description: "Kubernetes has scaled {{ $labels.hpa }} to max number of scaled pods."
-        dashboard: "OVH:<MONITORING>/k8-deployment"
 
     - alert: KubernetesPodNotHealthy
       expr: kube_pod_status_phase{phase=~"Pending|Unknown|Failed"} == 1

package/src/helm-charts/prom-operator/rules/{leverege-rules.yaml.ovh → leverege-rules.yaml}

@@ -17,4 +17,3 @@ spec:
       annotations:
         summary: Apps are restarting frequently
         description: "{{ $labels.app }} is in a crash loop"
-        dashboard: "OVH:<MONITORING>/stackdriver"

package/src/helm-charts/prom-operator/rules/{postgres-rules.yaml.ovh → postgres-rules.yaml}

@@ -17,7 +17,6 @@ spec:
       annotations:
         summary: "Postgresql down"
         description: "Postgresql instance is down: check {{ $labels.release }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlRestarted
       expr: time() - pg_postmaster_start_time_seconds < 60
@@ -27,7 +26,6 @@ spec:
       annotations:
         summary: "Postgresql restarted"
         description: "Postgresql restarted: check {{ $labels.release }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlExporterError
       expr: pg_exporter_last_scrape_error > 0
@@ -37,7 +35,6 @@ spec:
       annotations:
         summary: "Postgresql exporter error for {{ $labels.release }}"
         description: "Postgresql exporter is showing errors. Metrics may be outdated"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlReplicationLag
       expr: (pg_replication_lag > 10) and ON(instance) (pg_replication_is_replica == 1)
@@ -47,7 +44,6 @@ spec:
       annotations:
         summary: "Postgresql replication lag"
         description: "PostgreSQL replication lag is going up (> 10s): check {{ $labels.release }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlTableNotVacuumed
       expr: (pg_stat_user_tables_last_autovacuum > 0) and (time() - pg_stat_user_tables_last_autovacuum > 60 * 60 * 24)
@@ -57,7 +53,6 @@ spec:
       annotations:
         summary: "Postgresql table not vacuumed"
         description: "Table has not been vacuum for 24 hours: check {{ $labels.instance }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlTableNotAutoAnalyzed
       expr: (pg_stat_user_tables_last_autoanalyze > 0) and (time() - pg_stat_user_tables_last_autoanalyze > 60 * 60 * 24)
@@ -67,7 +62,6 @@ spec:
       annotations:
         summary: "Postgresql table not analyzed (instance {{ $labels.instance }})"
         description: "Table {{ $labels.relname }} has not been analyzed for 24 hours: check {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlDeadLocks
       expr: rate(pg_stat_database_deadlocks{datname!~"template.*|postgres"}[1m]) > 0
@@ -77,7 +71,6 @@ spec:
       annotations:
         summary: "Postgresql dead locks"
         description: "PostgreSQL has dead-locks: check {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlSlowQueries
       expr: pg_slow_queries > 0
@@ -87,7 +80,6 @@ spec:
       annotations:
         summary: "Postgresql slow queries"
         description: "PostgreSQL executing slow queries"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlHighRollbackRate
       expr: rate(pg_stat_database_xact_rollback{datname!~"template.*"}[3m]) / rate(pg_stat_database_xact_commit{datname!~"template.*"}[3m]) > 0.02
@@ -97,7 +89,6 @@ spec:
       annotations:
         summary: "Postgresql high rollback rate on {{ $labels.release }} - {{ $labels.datname }}"
         description: "Ratio of transactions being aborted compared to committed is > 2 %"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlCommitRateLow
       expr: rate(pg_stat_database_xact_commit[1m]) < 10
@@ -107,7 +98,6 @@ spec:
       annotations:
         summary: "Postgresql commit rate low on {{ $labels.release }} - {{ $labels.datname }}"
         description: "Postgres seems to be processing very few transactions"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlLowXidConsumption
       expr: rate(pg_txid_current[1m]) < 5
@@ -117,7 +107,6 @@ spec:
       annotations:
         summary: "Postgresql low XID consumption on {{ $labels.release }} - {{ $labels.datname }}"
         description: "Postgresql seems to be consuming transaction IDs very slowly"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqllowXlogConsumption
       expr: rate(pg_xlog_position_bytes[1m]) < 100
@@ -127,7 +116,6 @@ spec:
       annotations:
         summary: "Postgresqllow XLOG consumption on {{ $labels.release }} - {{ $labels.datname }}"
         description: "Postgres seems to be consuming XLOG very slowly"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlWaleReplicationStopped
       expr: rate(pg_xlog_position_bytes[1m]) == 0
@@ -137,7 +125,6 @@ spec:
       annotations:
         summary: "Postgresql WAL-E replication stopped on {{ $labels.release }} - {{ $labels.datname }}"
         description: "WAL-E replication seems to be stopped"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlHighRateStatementTimeout
       expr: rate(postgresql_errors_total{type="statement_timeout"}[5m]) > 3
@@ -147,7 +134,6 @@ spec:
       annotations:
         summary: "Postgresql high rate statement timeout"
         description: "Postgres transactions showing high rate of statement timeouts on {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlHighRateDeadlock
       expr: rate(postgresql_errors_total{type="deadlock_detected"}[1m]) * 60 > 1
@@ -157,7 +143,6 @@ spec:
       annotations:
         summary: "Postgresql high rate deadlock"
         description: "Postgres detected deadlocks on {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlReplicationLabBytes
       expr: (pg_xlog_position_bytes and pg_replication_is_replica == 0) - on (environment) group_right(instance) (pg_xlog_position_bytes and pg_replication_is_replica == 1) > 1e+09
@@ -167,7 +152,6 @@ spec:
       annotations:
         summary: "Postgresql replication lab bytes"
         description: "Postgres Replication lag (in bytes) is high on {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlTooManyDeadTuples
       expr: ((pg_stat_user_tables_n_dead_tup > 10000) / (pg_stat_user_tables_n_live_tup + pg_stat_user_tables_n_dead_tup)) >= 0.1 unless ON(instance) (pg_replication_is_replica == 1)
@@ -177,7 +161,6 @@ spec:
       annotations:
         summary: "Postgresql too many dead tuples"
         description: "PostgreSQL dead tuples is too large ( {{ $value }} dead tuples) on {{ $labels.release }} - {{ $labels.datname }}"
-        dashboard: "OVH:<MONITORING>/postgres"
 
     - alert: PostgresqlTooManyLocksAcquired
       expr: ((sum (pg_locks_count)) / (pg_settings_max_locks_per_transaction * pg_settings_max_connections)) > 0.20
@@ -187,4 +170,3 @@ spec:
       annotations:
         summary: "Postgresql too many locks acquired on {{ $labels.statefulset.kubernetes.io_pod_name }}"
         description: "Too many locks acquired on the database. If this alert happens frequently, we may need to increase the postgres setting max_locks_per_transaction."
-        dashboard: "OVH:<MONITORING>/postgres"

package/src/helm-charts/prom-operator/rules/{redis-rules.yaml.ovh → redis-rules.yaml}

@@ -16,7 +16,6 @@ spec:
       annotations:
         summary: "Redis down (instance {{ $labels.instance }})"
         description: "Redis instance is down"
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisMissingMaster
       expr: count(redis_instance_info{role="master"}) == 0
@@ -26,7 +25,6 @@ spec:
       annotations:
         summary: "Redis missing master (instance {{ $labels.instance }})"
         description: "Redis cluster has no node marked as master."
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisTooManyMasters
       expr: count(redis_instance_info{role="master"}) > 1
@@ -36,7 +34,6 @@ spec:
       annotations:
         summary: "Redis too many masters (instance {{ $labels.instance }})"
         description: "Redis cluster has too many nodes marked as master."
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisDisconnectedSlaves
       expr: count without (instance, job) (redis_connected_slaves) - sum without (instance, job) (redis_connected_slaves) - 1 > 1
@@ -46,7 +43,6 @@ spec:
       annotations:
         summary: "Redis disconnected slaves (instance {{ $labels.instance }})"
         description: "Redis not replicating for all slaves. Consider reviewing the redis replication status."
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisReplicationBroken
       expr: delta(redis_connected_slaves[1m]) < 0
@@ -56,7 +52,6 @@ spec:
       annotations:
         summary: "Redis replication broken (instance {{ $labels.instance }})"
         description: "Redis instance lost a slave"
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisClusterFlapping
       expr: changes(redis_connected_slaves[5m]) > 2
@@ -66,7 +61,6 @@ spec:
       annotations:
         summary: "Redis cluster flapping (instance {{ $labels.instance }})"
         description: "Changes have been detected in Redis replica connection. This can occur when replica nodes lose connection to the master and reconnect (a.k.a flapping)."
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisOutOfMemory
       expr: redis_memory_used_bytes / redis_total_system_memory_bytes * 100 > 90
@@ -76,7 +70,6 @@ spec:
       annotations:
         summary: "Redis out of memory (instance {{ $labels.instance }})"
         description: "Redis is running out of memory ( {{ $value }}% )"
-        dashboard: "OVH:<MONITORING>/redis"
 
     - alert: RedisRejectedConnections
       expr: increase(redis_rejected_connections_total[1m]) > 0
@@ -86,5 +79,3 @@ spec:
       annotations:
         summary: "Redis rejected connections (instance {{ $labels.instance }})"
         description: "Some connections to Redis has been rejected. Please check {{ $labels.app }}"
-        dashboard: "OVH:<MONITORING>/redis"
-

package/src/helm-charts/prom-operator/rules/{traefik-rules.yaml.ovh → traefik-rules.yaml}

@@ -25,4 +25,3 @@ spec:
 #     annotations:
 #       summary: "Traefik high HTTP 4xx error rate on {{ $labels.service }}"
 #       description: "Traefik backend 4xx error rate is above 10% (currently at {{ $value }}%)"
-#       dashboard: "OVH:<MONITORING>/traefik"

package/src/helm-charts/prom-operator/rules/{velero-rules.yaml.ovh → velero-rules.yaml}

@@ -16,7 +16,6 @@ spec:
       annotations:
         summary: "Velero schedule {{ $labels.schedule }} backup failed to execute properly"
         description: "It has been over 30 hours since the last successful backup"
-        dashboard: "OVH:<MONITORING>/velero"
     - alert: NoVeleroBackups
       expr: velero_backup_success_total{schedule!=""}  == 0
       for: 30h
@@ -25,4 +24,3 @@ spec:
       annotations:
         summary: "Velero has not made any backups yet"
         description: "No backups have successfully been made since velero was initialized (or restarted), go check it out ASAP"
-        dashboard: "OVH:<MONITORING>/velero"

package/src/helm-charts/resource-server/values-local.yaml

@@ -4,7 +4,7 @@
 #     - npm run sequelizeRunMigrations
 #
 image:
-  tag: # v1.5.1
+  tag: # v1.7.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/scheduler/values-local.yaml

@@ -1,5 +1,5 @@
 image:
-  tag: # v3.1.2
+  tag: # v3.3.0
 
 config:
   LOG_CONFIG: '{"type":"pino","level":"warn"}'

package/src/helm-charts/transponder-bq/values-local.yaml

@@ -1,7 +1,7 @@
 nameOverride: transponder-bq
 
 image:
-  tag: # v5.2.4
+  tag: # v5.3.4
 
 config:
   TRANSPONDER_RUN_MODE: "bigQueryJson"

package/src/helm-charts/transponder-dh/values-local.yaml

@@ -1,7 +1,7 @@
 nameOverride: transponder-dh
 
 image:
-  tag: # v5.2.4
+  tag: # v5.3.4
 
 config:
   TRANSPONDER_RUN_MODE: "denseHistoryCombined"

package/src/helm-charts/transponder-rt/values-local.yaml

@@ -1,7 +1,7 @@
 nameOverride: transponder-rt
 
 image:
-  tag: # v5.2.4
+  tag: # v5.3.4
 
 config:
   TRANSPONDER_RUN_MODE: "rt"

package/src/helm-charts/transponder-tsdb/values-local.yaml

@@ -7,7 +7,7 @@
 nameOverride: transponder-tsdb
 
 image:
-  tag: # v5.2.4
+  tag: # v5.3.4
 
 config:
   TRANSPONDER_RUN_MODE: "timescale"

package/src/helm-charts/vin-decoder-server/values-local.yaml

@@ -0,0 +1,7 @@
+image:
+  tag: # v4.1.0
+
+config:
+  LOG_CONFIG: '{"type":"pino","level":"warn"}'
+  PROJECT_ID: "set-in-values-local"
+  SYSTEM_ID: "set-in-values-local"

package/src/hook-and-release/Config.mjs

@@ -44,29 +44,18 @@ const cliSections = [
 handle git hooks in standard git repositories as well as git monorepos. It
 connects into a repository's git hook system after a repo is cloned. The hook
 connection is made during the {yellow.bold npm install} phase, which will execute the
-{yellow.bold npm prepare} script as defined in the package.json scripts section:
+{yellow.bold npm prepare} script as defined in the package.json scripts section.
 
   {yellow.bold "scripts": {
     ...
     "prepare": "[ $SKIP_PREPARE ] && exit 0 || hook-and-release",
     ...
-  }
+  \\} }
 
-Note the {yellow SKIP_PREPARE} flag will be set in the docker-to-registry Dockerfile
-template in order to avoid setting up the hooks during the image build
+The {yellow SKIP_PREPARE} flag will be set in the {yellow docker-to-registry} Dockerfile
+template in order to avoid setting up the hook during the image build
 process. The hook is only relevant when doing local development and is
 totally divorced from the image building process.
-
-The hook-and-release script can be invoked directly from the command line,
-typically for first-time initialization, or from the git hook scripts located
-in the .har subdirectory in the root of a repository. Running with the {yellow.bold --init}
-command line switch will create the .har subdirectory at the repo root with a
-config.json file and two standard hook scripts, pre-commit and pre-push:
-
-  {yellow.bold .har
-  ├── config.json
-  ├── pre-commit
-  └── pre-push}
 }`
   },
   {
@@ -74,8 +63,21 @@ config.json file and two standard hook scripts, pre-commit and pre-push:
     optionList : cliOptionList,
   },
   {
-    header : 'Configuration File and Hook Scripts',
+    header : `
+Configuration Setup and Hook Scripts`,
     content : [
+      `{green To add hook-and-release to a repository simply run:
+
+  {yellow.bold hook-and-release --init}
+
+which will create the {yellow.bold .har} subdirectory at the repo root with a {yellow.bold config.json}
+file and two standard hook scripts, {yellow.bold pre-commit} and {yellow.bold pre-push}:
+
+  {yellow.bold .har
+  ├── config.json
+  ├── pre-commit
+  └── pre-push}
+}`,
       `{bold .har/config.json}   {green controls branch, script and package config
 {white.bold protected-branches} list of branch names to protect
 {white.bold npm-scripts}        list of npm scripts to run on protected branches
@@ -98,11 +100,11 @@ config.json file and two standard hook scripts, pre-commit and pre-push:
 
 {white.bold Example pre-commit script file contents}
 
-  hook-and-release --debug
+  {yellow hook-and-release --debug}
 
-which tell HAR to run with debugging enabled. This will print out copious
+which tells HAR to run with debugging enabled. This will display copious
 amounts of information and prevents the git command from succeeding, so
-it's more like a debug with dry-run. Removing the {yellow.bold --debug} will
+it's more like a debug with dry-run. Removing the {yellow --debug} will
 allow everything to run normally.
 }`
     ]
@@ -140,6 +142,7 @@ export default class Config {
 
     if ( this.cliArgs.init ) {
       await this.initializeConfiguration( this.harDir )
+      process.exit( 0 )
     }
 
     // Start with the basics, is there a root har directory?
@@ -224,6 +227,14 @@ export default class Config {
 
     makeHarHookScript( `${harDir}/pre-commit` )
     makeHarHookScript( `${harDir}/pre-push` )
+
+    const huskyWarningAndPrepare = `
+    Heads Up! Remove ${chalk.red.bold( 'husky' )} references from the package.json dependencies
+    and replace the ${chalk.yellow.bold( 'prepare' )} script with this:
+
+    ${chalk.green.bold( '"prepare": "[ $SKIP_PREPARE ] && exit 0 || hook-and-release",' )}
+`
+    log( huskyWarningAndPrepare )
   }
 
   async runNpmScripts( runDirectories = [] ) {

package/src/pkgck.sh

@@ -39,6 +39,14 @@ check_babel () {
   printf $C_stat
 }
 
+check_har () {
+  local C_stat=$(bad)
+  local prep="`node -p \"require('./package.json').scripts.prepare\"`"
+  local isHar=`echo $prep | egrep -e "hook-and-release"`
+  [ ! -z "$isHar" ] && C_stat=$(good)
+  printf $C_stat
+}
+
 check_circle () {
   local C_stat=$(bad)
   [ -f ".circleci/config.yml" ] && C_stat=$(good)
@@ -128,13 +136,14 @@ check_repo() {
     [ $? -ne 0 ] && needspush='!tags'
   fi
   local babel7=$(check_babel)
+  local hookar=$(check_har)
   local circle=$(check_circle)
   local eslint=$(check_eslint)
   local esmlib=$(check_ESM)
   local license=$(check_license)
   local scoped=$(check_scope)
-  [ $(( $repos % 15)) -eq 0 ] && printf "\n%35s pkg      git  cln scop cir lic ESM bl7\n"
-  printf "%32s: %-8s %-16s %s  %8s  %s   %s   %s   %s  %s\n" ${dir:0:32} $pkgver $(check_git_version $gitver $pkgver) $localmods $scoped $circle $license $esmlib $babel7 "$needspush"
+  [ $(( $repos % 15)) -eq 0 ] && printf "\n%35s pkg      git  cln scop cir lic ESM har\n"
+  printf "%32s: %-8s %-16s %s  %8s  %s   %s   %s   %s  %s\n" ${dir:0:32} $pkgver $(check_git_version $gitver $pkgver) $localmods $scoped $circle $license $esmlib $hookar "$needspush"
   let "repos++"
   cd - &> /dev/null
 }

package/src/helm-charts/prom-operator/rules/gitignore

@@ -1 +0,0 @@
-*.yaml