8000 test(server): cover static push auth across actor changes by opsmon · Pull Request #255 · aenix-io/aeman · GitHub
[go: up one dir, main page]

Skip to content

test(server): cover static push auth across actor changes - #255

Merged
kvaps merged 1 commit into
aenix-io:mainfrom
opsmon:issue-188
Nov 2, 2026
Merged

kvaps merged 1 commit into
aenix-io:mainfrom
opsmon:issue-188

Conversation

@opsmon
@opsmon opsmon commented Sep 27, 2026
Copy link
Copy Markdown
Contributor

Summary

Add end-to-end regression coverage for the intended authentication asymmetry:

  • push credentials are resolved once when the backend starts
  • request attribution continues to follow the current credential owner
  • restarting resolves the new push credential
  • GitHub App renewal behavior and production authentication policy remain unchanged

The test observes actual receive-pack authentication and persisted remote commit attribution.

Testing

  • full HTTP mutation, queue drain, Git push, and remote-history verification
  • separate dynamic-push-auth and frozen-actor mutation proofs
  • full local CI-equivalent suite with the race detector

Fixes #188

Exercise the full HTTP mutation, commit, drain, and receive-pack path while a credential source moves from Alice/token A to Bob/token B. Verify that the running backend keeps token A for pushes while request attribution follows Bob, then that a restart resolves token B.

This adds regression coverage for the intended asymmetry and does not change authentication policy.

Fixes aenix-io#188

Assisted-by: LLM
@kvaps
kvaps merged commit f953acd into aenix-io:main Nov 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Nothing tests that the push credential is fixed at start-up while the actor is not

2 participants

0