demo-web-ng-fastpath
Skill932 starsChanged 12 days agoApache-2.0View on GitHub
Refresh the Kubernetes `demo` namespace with a web-ng-only change using the ServiceRadar fast path. Use when the diff only touches `elixir/web-ng/**` and the user wants a faster demo rollout than the full image graph. Covers scope verification, the in-cluster `publish-oci.yml` web-stack-commit-only build, copying unchanged images forward, signing with the OpenBao release key, the pin PR into `demo/prod-release`, and verifying the rollout. Do not use when non-web-ng services changed or when cutting a release.
- Sends data out
- Commits and pushes
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/AGENTS.mdAGENTS.md
- openspec/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- daisyuiSkill
- demo-cnpg-local-web-ngSkill
- demo-local-rolloutSkill
- fieldsurvey-local-web-ngSkill
- playwright-cliSkill
- release-cut-and-demo-rollSkill
- serviceradar-bazel-guardrailsSkill
- serviceradar-build-testSkill
- serviceradar-dependenciesSkill
- serviceradar-elixirSkill
- serviceradar-openspecSkill
- serviceradar-operationsSkill
- srql-fixtures-db-testsSkill
- web-ng-docker-loopSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. About 0 are common, 5 are distinctive, and 10 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
10
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 18
Verify the diff only touches elixir/web-ng/.
- Distinctive: line 22
Verify every image at the new tag and sign the new web-ng and core-elx digests.
- Distinctive: line 24
After merge, watch Argo and the key workloads until the rollout completes.
- Very specific: line 28
Use this only when the diff is actually web-ng-only.
- Very specific: line 29
Do not use this for release cuts or any namespace other than demo unless the user explicitly redirects you.
- Very specific: line 30
Do not build the image on a workstation.
- Very specific: line 31
Do not leave a formal release rollout on a sha-...
- Very specific: line 32
Do not skip signing. demo admission is Kyverno-enforced, and the web-stack-commit-only publish does not sign.
- Very specific: line 34
Never push to staging or demo/prod-release.
- Very specific: line 91
Do not copy serviceradar-core-elx or serviceradar-web-ng.
- Very specific: line 98
Run the verify loop from $demo-local-rollout (demo roll, step 3) over all 15 images at sha-<new>.
- Distinctive: line 118
Do not re-derive them.
- Distinctive: line 145
Keep the JWT and Vault token in files.
- Distinctive: line 162
Check the key deployments:
- Very specific: line 177
Do not report success until the new serviceradar-web-ng pod is running on the new tag and Argo reaches Succeeded for the pin PR's merge …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Demo Web-NG Fast Path
Overview
Use this skill when a change is isolated to elixir/web-ng/** and the goal is to test it in demo quickly. Build only serviceradar-web-ng (and serviceradar-core-elx, which the same build step produces) in-cluster, copy the other demo images forward to the new immutable tag, sign the new digests, pin the tag with a PR into demo/prod-release, and verify the rollout.
Formal releases use semver tags, such as v1.2.41, and $release-cut-and-demo-roll. This skill is only for temporary unpublished sha-... demo testing. The signing commands, the pin PR, and the Argo checks are shared with $demo-local-rollout (demo roll, steps 3 to 5); follow them there rather than keeping a second copy here.
Workflow
- Work from the repo root.
- Determine the new immutable tag:
sha-$(git rev-parse <commit>). - Verify the diff only touches
elixir/web-ng/**. - Identify the currently deployed
demotag. - Push a
test/demo-test-NNbranch at the commit and dispatchpublish-oci.ymlwithpublish_scope=web-stack-commit-only. - Copy every other
demoimage from the old tag to the new tag. - Verify every image at the new tag and sign the new web-ng and core-elx digests.
- Open the pin PR into
demo/prod-release. - After merge, watch Argo and the key workloads until the rollout completes.
Guardrails
- Use this only when the diff is actually
web-ng-only. If anything outsideelixir/web-ng/**changed, fall back to$demo-local-rollout. - Do not use this for release cuts or any namespace other than
demounless the user explicitly redirects you. - Do not build the image on a workstation. A workstation Bazel build of the image set pulls large CAS blobs through
cache-proxy.carverauto.devand has OOMKilled the shared Envoy gateway; the in-cluster build avoids that. - Do not leave a formal release rollout on a
sha-...tag. After testing is complete, use$release-cut-and-demo-rollto returndemoto the published semver path. - Do not skip signing.
demoadmission is Kyverno-enforced, and the web-stack-commit-only publish does not sign. - Sign by digest, not by tag.
- Never push to
stagingordemo/prod-release; push new branches with an explicit refspec (git push origin <local>:refs/heads/<branch>).
Verify The Scope First
Run:
git fetch origin demo/prod-release
git show origin/demo/prod-release:helm/serviceradar/.argocd-source-serviceradar-demo-prod.yaml
git diff --name-only <currently-deployed-sha>..<commit>Proceed only if every changed file is under elixir/web-ng/.
Build In-Cluster
COMMIT="$(git rev-parse <commit>)"
git ls-remote origin 'refs/heads/test/demo-test-*' # pick the next unused NN
git push origin "${COMMIT}:refs/heads/test/demo-test-<NN>"
gh workflow run publish-oci.yml --ref "test/demo-test-<NN>" \
-f publish_scope=web-stack-commit-only -f expected_commit="${COMMIT}"
gh run list --workflow publish-oci.yml --branch "test/demo-test-<NN>" --limit 1
gh run watch <run-id> --exit-statusexpected_commit must equal the branch head exactly or the run refuses to
publish. The run pushes only serviceradar-core-elx:sha-<COMMIT> and
serviceradar-web-ng:sha-<COMMIT> (no latest), writes both digests to the
step summary, and does not sign them.
Copy Unchanged Images Forward
Copy the other images from the current demo tag to the new tag with crane (on PATH via Homebrew):
crane copy \
registry.carverauto.dev/serviceradar/<image>:<old-tag> \
registry.carverauto.dev/serviceradar/<image>:sha-<new>Repeat for:
aranciniserviceradar-agentserviceradar-agent-gatewayserviceradar-datasvcserviceradar-db-event-writerserviceradar-fakerserviceradar-flow-collectorserviceradar-log-collectorserviceradar-rperf-clientserviceradar-toolsserviceradar-trapdserviceradar-trivy-sidecarserviceradar-zen
Do not copy serviceradar-core-elx or serviceradar-web-ng; the run already
pushed them at the new tag. A copy keeps the digest, so the copied images keep
their existing signatures. Leave serviceradar-log-collector-tcp alone; it
shares the log-collector image.
Verify And Sign
Run the verify loop from $demo-local-rollout (demo roll, step 3) over all 15
images at sha-<new>. Expect serviceradar-web-ng and serviceradar-core-elx
to be UNSIGNED; sign those digests with the github-signing-runner flow in
that step, then re-run the loop until every image reports signed.
Pin And Roll
Open the pin PR into demo/prod-release setting global.imageTag to
sha-<new>, and confirm the automated Argo sync, exactly as in
$demo-local-rollout (demo roll, steps 4 and 5). List existing
image.digests.<service> parameters in
helm/serviceradar/.argocd-source-serviceradar-demo-prod.yaml and remove the
pin for every service that should move in the same PR: a digest pin overrides
global.imageTag. Do not patch the Argo
Application: the .argocd-source-... file replaces its parameters (see
Verified Facts).
Verified Facts (2026-08-22, live run)
These were each confirmed against the live carverauto cluster during a real web-ng roll.
Do not re-derive them.
- For the OpenBao endpoint, signing identity, and token handling, follow
$demo-local-rollout(demo roll, step 3). .argocd-source-serviceradar-demo-prod.yamlREPLACEShelm.parametersat render time. This is stronger than a race: akubectl patchofspec.source.helm.parametersonserviceradar-demo-prodpersists in the Application spec, syncsSynced|Healthy|Succeeded, and is still completely ignored -- only the parameters listed in that file ondemo/prod-releasereach Helm. Any parameter you need (global.imageTag,image.digests.*) must be committed to that file ondemo/prod-release.image.digests.<service>is a real per-service escape hatch (_helpers.tplserviceradar.imageRefSuffix): it short-circuits ahead of the tag, so you can move ONE service and leave every other image on the already-signed release tag -- one signature instead of fifteen. Service key for web-ng iswebNg. It still has to go in the.argocd-source-...file to take effect.- A full-scope publish moves
lateston every image (oci_pushcarriesstatic_tags = ["latest"]; this coverspublish-oci.ymlpublish_scope=fulland the workstationmake push_all). Theweb-stack-commit-onlyscope pushes onlysha-<commit>. It does NOT movev<VERSION>:scripts/workspace_status.shemitsSTABLE_VERSION devunless a matchingv<VERSION>git tag points at HEAD, andcontainer_tags.bzlfiltersvdev. Verify withgit tag --points-at HEADbefore pushing. - Claude Code auto mode blocks the signing flow unless these allow rules exist in
.claude/settings.local.json, and the commands are run discretely (abash -c '...'wrapper defeats prefix matching):Bash(kubectl --context carverauto create token:*),Bash(curl -sS -k -X POST --data:*),Bash(cosign sign:*),Bash(cosign verify:*). Keep the JWT and Vault token in files; never put them on a command line.
Verify Rollout
Wait for:
Synced|Healthy|SucceededUse:
kubectl get application -n argocd serviceradar-demo-prod \
-o jsonpath='{.status.sync.status}{"|"}{.status.health.status}{"|"}{.status.operationState.phase}{"\n"}'Check the key deployments:
kubectl get deploy -n demo \
serviceradar-web-ng serviceradar-core serviceradar-agent serviceradar-tools \
-o jsonpath='{range .items[*]}{.metadata.name}{"\t"}{range .spec.template.spec.containers[*]}{.image}{" "}{end}{"\n"}{end}'Inspect pods and jobs if Argo is still Progressing:
kubectl get pods -n demo -o wide
kubectl get jobs -n demoDo not report success until the new serviceradar-web-ng pod is running on the new tag and Argo reaches Succeeded for the pin PR's merge revision (.status.sync.revision).
Report Back
Close with:
- target immutable tag
- old tag that was copied forward
- publish run id and test branch
- web-ng and core-elx digests that were signed
- pin PR
- final Argo status
- any lingering rollout risk
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

