Fix scaffold to match SERVICE_ONBOARDING.md conventions #3
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/basketball-api#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Context
PR #2 (scaffold) passed a 4-round review but diverges from SERVICE_ONBOARDING.md in multiple ways. basketball-api should be a reference implementation of the platform, not a deviation.
Deviations to Fix
.woodpecker.yaml
docker:27instead ofwoodpeckerci/plugin-kaniko:2.3.0${CI_COMMIT_SHA:0:7}(7-char) instead of$CI_COMMIT_SHA(full SHA)k8s/.argocd-source-*needs to be full path patternpytesttest stepk8s manifests
namespace: basketball-apion all resourcesport: 8000, targetPort: 8000, name: httpservicemonitor.yamlkustomization.yamlmissing servicemonitor resourceApplication
/metricsendpoint stub (Prometheus scraping)Related
Closing — app is deployed and running in production. Scaffold divergences from SERVICE_ONBOARDING.md are not blocking and not worth retrofitting at this point. Future repos should use the onboarding SOP from the start.