Skip to content

feat(exesh): send internal auth with heartbeats - #342

Draft
DIvanCode wants to merge 1 commit into
masterfrom
codex/324-exesh-internal-auth
Draft

feat(exesh): send internal auth with heartbeats#342
DIvanCode wants to merge 1 commit into
masterfrom
codex/324-exesh-internal-auth

Conversation

@DIvanCode

Copy link
Copy Markdown
Owner

Closes#324

Exesh workers now read InternalAuthKey and send it with every coordinator heartbeat. Local and end-to-end worker/coordinator configurations use INTERNAL_AUTH_KEY_LOCAL_VALUE; the deployment playbook passes one encrypted internal_auth_key to the coordinator and both workers and validates it before deployment work begins. The heartbeat process documentation records the authenticated request.

Operator action before Ready for review: add the same non-local internal_auth_key to the encrypted credentials used by Duely, Taski, Exesh, and later Analyzer. Do not commit the plaintext value.

Validation:

  • go test ./...
  • ./e2e/taski-exesh/run.sh — accepted A+B solution
  • ansible-playbook --syntax-check with temporary non-secret test variables

Sign up for freeto 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.

[internal-auth][Exesh] Подкладывать заголовок internal-auth в межсервисные запросы

1 participant

@DIvanCode