→ page loads with the filter input pre-filled with connectivity_tester, applied immediately, only matching stacks visible.
Acceptance
?filter=<text> in the URL pre-fills the filter input.
Filter is applied on initial render (not just pre-filled but unapplied).
Multiple words: ?filter=connectivity_tester%20hermes_infra — both substrings must match (current filter behaviour).
Empty ?filter= behaves as if no param was passed (no pre-fill, no apply).
Existing behaviour without the param is unchanged.
Works on the main page (stack list) and any page that has a filter input.
Blocks
Org1/hermes-voice-gateway#5 (connectivity testing container) — once brencher deploys the new stack, the UI should deep-link to it via filter for quick access from the Gitea issue body or other dashboards.
admin/brencher#65 (PR) — once merged, you need an easy way to find the new stack in the UI without scrolling.
## Request
Brencher UI should accept a `filter` GET-parameter. If present, the value is auto-inserted into the filter input on page load.
## Use case
Quickly deep-link to a filtered view from external tooling, runbooks, or other UIs. Example:
`https://brencher.rudolf.keenetic.link/?filter=connectivity_tester`
→ page loads with the filter input pre-filled with `connectivity_tester`, applied immediately, only matching stacks visible.
## Acceptance
- `?filter=<text>` in the URL pre-fills the filter input.
- Filter is applied on initial render (not just pre-filled but unapplied).
- Multiple words: `?filter=connectivity_tester%20hermes_infra` — both substrings must match (current filter behaviour).
- Empty `?filter=` behaves as if no param was passed (no pre-fill, no apply).
- Existing behaviour without the param is unchanged.
- Works on the main page (stack list) and any page that has a filter input.
## Blocks
- Org1/hermes-voice-gateway#5 (connectivity testing container) — once brencher deploys the new stack, the UI should deep-link to it via filter for quick access from the Gitea issue body or other dashboards.
- admin/brencher#65 (PR) — once merged, you need an easy way to find the new stack in the UI without scrolling.
Cross-references (Gitea IssueDependencies API throws 404 for cross-repo links, so I am noting them in a comment):
admin/brencher#65 (PR feat(configs): add connectivity_tester stack) is blocked by this issue. Until the parameterised env+ref filter is implemented, #65 ships hardcoded values which makes the stack non-configurable per cluster.
Org1/hermes-voice-gateway#5 (Connectivity testing container) is upstream — it describes the original need for per-cluster EXTRA_ENDPOINTS, which this issue is a prerequisite to support.
Cross-references (Gitea IssueDependencies API throws 404 for cross-repo links, so I am noting them in a comment):
- admin/brencher#65 (PR feat(configs): add connectivity_tester stack) is **blocked by** this issue. Until the parameterised env+ref filter is implemented, #65 ships hardcoded values which makes the stack non-configurable per cluster.
- Org1/hermes-voice-gateway#5 (Connectivity testing container) is **upstream** — it describes the original need for per-cluster EXTRA_ENDPOINTS, which this issue is a prerequisite to support.
hermes
changed title from brencher: support parameterised env+ref filter (auto-inserted into stack config) to brencher UI: support ?filter=<text> GET-param that auto-fills the filter input2026-09-14 17:51:06 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Request
Brencher UI should accept a
filterGET-parameter. If present, the value is auto-inserted into the filter input on page load.Use case
Quickly deep-link to a filtered view from external tooling, runbooks, or other UIs. Example:
https://brencher.rudolf.keenetic.link/?filter=connectivity_tester→ page loads with the filter input pre-filled with
connectivity_tester, applied immediately, only matching stacks visible.Acceptance
?filter=<text>in the URL pre-fills the filter input.?filter=connectivity_tester%20hermes_infra— both substrings must match (current filter behaviour).?filter=behaves as if no param was passed (no pre-fill, no apply).Blocks
Cross-references (Gitea IssueDependencies API throws 404 for cross-repo links, so I am noting them in a comment):
brencher: support parameterised env+ref filter (auto-inserted into stack config)to brencher UI: support ?filter=<text> GET-param that auto-fills the filter input