Block a user
johnride
pushed to refactor/smoke-companion-minimal at NationTech/harmony
2026-05-26 10:56:20 +00:00
johnride
created branch refactor/smoke-companion-minimal in NationTech/harmony
2026-05-26 10:56:20 +00:00
johnride
deleted branch docs/update-fleet-architecture from NationTech/harmony
2026-05-25 12:40:36 +00:00
9cea7148a0
Merge pull request 'Upate HTML for fleet/ARCHITECTURE.html' (#298) from docs/update-fleet-architecture into master
Upate HTML for fleet/ARCHITECTURE.html
feat(fleet-deploy): smoke-test contract as a Score companion
This all looks correct, but I have a feeling we could find a simpler design that does not involve the whole smokesuite -> smoke -> probe -> probeoutcome -> probestatus boilerplate.
feat(fleet-deploy): smoke-test contract as a Score companion
Idea : associate an interpret type instead? The idea is that we have many scores that point to the same interpret. Of course locking to a score makes the code smaller and easier to understand, but will inevitably lead to boilerplate and a lot of repetition when similar scores exist. For example a smoke test on a HelmChartScore that valudates the helm chart is ready would not work with a NatsHelmChartScore as it is not the same type at the top level but would work with both if we use the Interpret type which is the same for both.
269ab2fbed
Merge pull request 'docs(fleet): v0.3 last-mile roadmap' (#296) from docs/v0-3-roadmap into feat/smoke-test-contract
docs(fleet): v0.3 last-mile roadmap
docs(fleet): v0.3 last-mile roadmap
feat(fleet-deploy): log-tail contract as a Score companion
feat/v0-3-operator-restart-baseline
feat/v0-3-dashboard-role-enforcement
johnride
pushed to feat/v0-3-dashboard-role-enforcement at NationTech/harmony
2026-05-25 10:45:45 +00:00