roger/k3s-cluster
1
0
Fork 1
Code Issues Pull Requests 6 Actions Packages Projects Releases Wiki Activity

fix(myorg-assistant): add missing GIT_TOKEN to deadline-checker CronJob #25

Open
platform-engineer-agent wants to merge 2 commits from platform-engineer-agent/k3s-cluster:fix/deadline-checker-git-token into main
pull from: platform-engineer-agent/k3s-cluster:fix/deadline-checker-git-token
merge into: roger:main
Conversation 0 Commits 2 Files Changed 4 +60
platform-engineer-agent commented 2026-07-16 03:18:21 +02:00
Collaborator
Copy Link

The deadline-checker CronJob pod crashed at import with pydantic ValidationError (git_token field required) because it did not mount GIT_TOKEN/GIT_REPO_URL/GIT_USERNAME from myorg-assistant-secret, unlike the main Deployment. Added the three git-related secret env vars so Settings() validates.

Diagnosed via Loki: pydantic ValidationError: 1 validation error for Settings ... git_token ... Field required.

The deadline-checker CronJob pod crashed at import with pydantic ValidationError (git_token field required) because it did not mount GIT_TOKEN/GIT_REPO_URL/GIT_USERNAME from myorg-assistant-secret, unlike the main Deployment. Added the three git-related secret env vars so Settings() validates. Diagnosed via Loki: pydantic ValidationError: 1 validation error for Settings ... git_token ... Field required.
platform-engineer-agent added 1 commit 2026-07-16 03:18:23 +02:00
fix(myorg-assistant): add missing GIT_TOKEN/GIT_REPO_URL/GIT_USERNAME to deadline-checker CronJob b5b4a3b250 
The deadline-checker container crashed at import (pydantic ValidationError:
git_token field required) because the CronJob pod did not mount GIT_TOKEN
from myorg-assistant-secret, unlike the main Deployment. Added the three
git-related secret env vars so Settings() validates.
platform-engineer-agent added 1 commit 2026-07-16 03:19:19 +02:00
fix(myorg-assistant): add missing GIT_TOKEN to all CronJob pods (deadline-checker, morning-briefing, evening-summary, waiting-followup) 483d23ba63 
All four CronJobs share the same image + run_job entrypoint and import
Settings(), which requires git_token. Only git-sync and the Deployment
supplied these. Added GIT_REPO_URL/GIT_USERNAME/GIT_TOKEN secret env vars
to the other three CronJobs to prevent the same pydantic ValidationError
crash at import.
This pull request has changes conflicting with the target branch.
  • myorg-assistant/cronjobs/deadline-checker.yaml
  • myorg-assistant/cronjobs/evening-summary.yaml
  • myorg-assistant/cronjobs/morning-briefing.yaml
  • myorg-assistant/cronjobs/waiting-followup.yaml
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u fix/deadline-checker-git-token:platform-engineer-agent-fix/deadline-checker-git-token
git checkout platform-engineer-agent-fix/deadline-checker-git-token
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
platform-engineer-agent roger
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: roger/k3s-cluster#25
No description provided.
Delete Branch "platform-engineer-agent/k3s-cluster:fix/deadline-checker-git-token"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?