ScottyLabs/collar
Watch
24
0
Fork
You've already forked collar
 0
Code Issues 1 Pull requests 1 Projects Releases Packages Wiki Activity Actions

WIP: feat: authenticated Kennel log access #1

Draft
kritdass wants to merge 1 commit from feat/kennel-log-access into main
pull from: feat/kennel-log-access
merge into: ScottyLabs:main
Conversation 2 Commits 1 Files changed 1 +72
kritdass commented 2026-10-15 18:44:13 +00:00
Member
Copy link

Direct terminal log reads need an authenticated Kennel API so developers do not have to manage Grafana service-account tokens. This draft records the backend contract and intended collar kennel logs behavior; it deliberately does not ship the rejected token-based logcli adapter.

Required Kennel work:

  • Authenticated, authorized read-only build/deployment log endpoints, with project access checks.
  • Stable identifier discovery from repository plus full commit SHA, or machine-readable build/deployment IDs in status metadata.
  • Bounded Loki queries, line limits, pagination, and a documented follow protocol.
  • A supported SSO flow for CLI users and authorized automation. Forgejo tokens are not automatically Kennel credentials.

After that backend contract exists, collar kennel logs 42 should retrieve deployment logs directly, --build should select build logs, --follow should stream, and --links should retain Grafana URLs. Preserve the existing JSON report contract.

Current infrastructure already has a Grafana Loki proxy, but an unauthenticated read returns 401. Kennel currently has no user-authenticated API. Authentication and authorization are the dependency, not exposing Loki publicly.

Validation: proposal reviewed against current canonical Kennel routes, status-link generation, and infrastructure Grafana/Loki configuration. Repository hooks passed. No live resources were changed for testing.

Direct terminal log reads need an authenticated Kennel API so developers do not have to manage Grafana service-account tokens. This draft records the backend contract and intended `collar kennel logs` behavior; it deliberately does not ship the rejected token-based logcli adapter. Required Kennel work: - Authenticated, authorized read-only build/deployment log endpoints, with project access checks. - Stable identifier discovery from repository plus full commit SHA, or machine-readable build/deployment IDs in status metadata. - Bounded Loki queries, line limits, pagination, and a documented follow protocol. - A supported SSO flow for CLI users and authorized automation. Forgejo tokens are not automatically Kennel credentials. After that backend contract exists, `collar kennel logs 42` should retrieve deployment logs directly, `--build` should select build logs, `--follow` should stream, and `--links` should retain Grafana URLs. Preserve the existing JSON report contract. Current infrastructure already has a Grafana Loki proxy, but an unauthenticated read returns 401. Kennel currently has no user-authenticated API. Authentication and authorization are the dependency, not exposing Loki publicly. Validation: proposal reviewed against current canonical Kennel routes, status-link generation, and infrastructure Grafana/Loki configuration. Repository hooks passed. No live resources were changed for testing.
docs: propose authenticated kennel log access
Some checks failed
CI / build (pull_request) Has been skipped
Details
CI / package (pull_request) Successful in 21m30s
Details
CI / check (pull_request) Has been cancelled
Details
CI / check-1 (pull_request) Has been cancelled
Details
29c2684a92
kritdass commented 2026-10-15 18:46:15 +00:00
Author
Member
Copy link

@anish this is for the grafana integration because I think Loki tokens would be too unergonomic

@anish this is for the grafana integration because I think Loki tokens would be too unergonomic
kritdass force-pushed feat/kennel-log-access from 29c2684a92
Some checks failed
CI / build (pull_request) Has been skipped
Details
CI / package (pull_request) Successful in 21m30s
Details
CI / check (pull_request) Has been cancelled
Details
CI / check-1 (pull_request) Has been cancelled
Details
to 778ef018eb
All checks were successful
CI / build (pull_request) Has been skipped
Details
CI / package (pull_request) Successful in 2m18s
Details
CI / check-1 (pull_request) Successful in 9m47s
Details
CI / check (pull_request) Successful in 0s
Details
2026-10-15 19:20:07 +00:00 Compare
kritdass commented 2026-10-16 18:45:59 +00:00
Author
Member
Copy link

@thesuperRL would like your thoughts as well

@thesuperRL would like your thoughts as well
All checks were successful
CI / build (pull_request) Has been skipped
Details
CI / package (pull_request) Successful in 2m18s
Details
CI / check-1 (pull_request) Successful in 9m47s
Details
CI / check (pull_request) Successful in 0s
Details
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin feat/kennel-log-access:feat/kennel-log-access
git switch feat/kennel-log-access

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff feat/kennel-log-access
git switch feat/kennel-log-access
git rebase main
git switch main
git merge --ff-only feat/kennel-log-access
git switch feat/kennel-log-access
git rebase main
git switch main
git merge --no-ff feat/kennel-log-access
git switch main
git merge --squash feat/kennel-log-access
git switch main
git merge --ff-only feat/kennel-log-access
git switch main
git merge feat/kennel-log-access
git push origin main
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
  
needs/docs
Must have documentation written

  
needs/research
Discuss the ideal implementation with the tech lead

  
needs/upstream
Needs a contribution to an upstream project

  
type/bug
Something not working as intended

  
type/external
Lives outside of code

  
type/feature
New functionality

  
type/refactor
Improving existing code

  
urgency
high
 This is currently causing issues

  
urgency
immediate
 This is making a project or feature unusable

  
urgency
low
 This can happen whenever

  
urgency
medium
 This is expected to cause issues soon

No labels
needs/docs
needs/research
needs/upstream
type/bug
type/external
type/feature
type/refactor
urgency
high
urgency
immediate
urgency
low
urgency
medium
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
ScottyLabs/collar!1
No description provided.