Repository navigation
Tower UI fixes: one YAML look with Copy, Lambda cards, guardrails red after a bypass, new Ground env steps - #87
Merged
Merged
Conversation
… after a bypass, new Ground env steps - YAML everywhere goes through one kit piece, ui/YamlBlock (keys sky, numbers amber, line numbers, Copy, a line filter): the PipelineRun YAML dialog (it had no Copy), the committed cicd.yaml, a Rollout topology node, the values form's full/committed values and examples, and the topology YamlView's YAML mode. Five hand-rolled <pre> styles gone. - Services cards: the footer wraps, so "Function · AWS Lambda" no longer cuts the owner off; the owner sits right-aligned on its own line when needed. - Pull request dialog: one link to the PR, not two. - Deployments DAG: a merge that went ahead with a failed check (GitHub Free cannot block it) draws Guardrails red instead of green; the delivery still counts as finished, so it does not stay "current" for good. - Pipeline logs: archived (Tekton Results) logs now carry the watcher's per-line timestamps (gitops-cluster-dev#95) and are parsed like live logs. - Adding a Ground environment: the provisioning steps link the onboarding PR that is open (not the oldest merged one) and wait on it; the values file is re-read every 45 s until it exists; "Also add a deploy step for it to the pipeline" (on by default) gives the new environment a deploy step like a Flight one gets a release step, and the Deployed step says plainly when no pipeline deploys there. Replicas shows the chart default as a placeholder instead of a value the file never set. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…t a blocked merge The banner said "this blocks the merge, nothing has synced" for a release that had merged and rolled out with a failed check. The red Guardrails node and its stage detail carry that; the banner reports the rollout. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Works through the 2026-10-12 bug list (items 2, 3, 4, 7, 8, 9, 10; items 1, 5 and 6 live in backstage/glidepath).
ui/YamlBlock(keys sky, numbers/booleans amber, line numbers, Copy, line filter): the Pipelines YAML dialog, the committed cicd.yaml, a Rollout topology node, the values form's full/committed values and its examples, and the topology YamlView's YAML mode. Documented in docs/design-system.md.Function · AWS Lambdano longer cuts the owner off.Checks: tsc, 743 tests, lint (0 errors), style ratchet, package build (no chunk cycle).
🤖 Generated with Claude Code