7fa2b61b29
Tweaks to how execution time is tracked for more accuracy + excluding waiting states: - don't update if crawl state is in a 'waiting state' (waiting for capacity or waiting for org limit) - rename start states -> waiting states for clarity - reset lastUpdatedTime if two consecutive updates of non-running state, to ensure non-running states don't count, but also account for occasional hiccups -- if only one update detects non-running state, don't reset - webhooks: move start webhook to when crawl actually starts for first time (db lastUpdatedTime is not yet + crawl is running) - don't set lastUpdatedTime until pods actually running - set crawljob update interval to every 10 seconds for more accurate execution time tracking - frontend: show seconds in 'Execution Time' display |
||
|---|---|---|
| .. | ||
| admin/logging | ||
| app-templates | ||
| btrix-crds | ||
| charts | ||
| email-templates | ||
| examples | ||
| templates | ||
| test | ||
| .helmignore | ||
| Chart.lock | ||
| Chart.yaml | ||
| README.md | ||
| values.yaml | ||
Update Helm dependencies
- It needs to update Helm charts after changing its dependencies (e.g. logging)
$ helm dependency update .
Update metacontroller
#!/bin/bash
# intall metacontroller
git clone --depth=1 https://github.com/metacontroller/metacontroller.git
cd metacontroller
helm package deploy/helm/metacontroller --destination deploy/helm
cd ..
# update dependency
helm dependency update
- Bump up the metacontroller version in
Chart.yaml