Garment.id
🇮🇩 Indonesian
  • 🇮🇩 Indonesian
  • 🇺🇸 English
Home
Core APITenant APISupport CenterChangelog
Home
Core APITenant APISupport CenterChangelog
Github
Instagram
|
🇮🇩 Indonesian
  • 🇮🇩 Indonesian
  • 🇺🇸 English
🇮🇩 Indonesian
  • 🇮🇩 Indonesian
  • 🇺🇸 English
  1. Home
  • Introduction
  • 01 - Project Structure
  • 02 - Context Boundaries
  • 03 - Central Auth Runtime
  • 04 - Central Billing
  • 05 - Tenant Runtime
  • 06 - FE Integration Contracts
  • 07 - Security, Middleware, and RLS
  • 08 - Events, Jobs, Listeners, Notifications, Observers
  • 09 - Testing and Quality Gates
  • 10 - Operations Runbook
  • 11 - Architecture Decisions (ADR Ringkas)
  • 12 - API Endpoint Catalog (v1)
  • 13 - Class Catalog by Context
  • 14 - Feature Development Playbook
  • 15 - Migration and Model Conventions
  • 16 - Service, Support, and Trait Contracts
  • 17 - Auth Business Scenarios and Decision Tree
  • 18 - Config Reference and Impact
  • 19 - Migration and Model Cookbook
  • 20 - Billing and Provisioning Business Flows
  • 21 - FE Error Handling Matrix
  • 22 - Incident Playbooks
  • 23 - Data Ownership Matrix
  • 24 - Documentation Governance and Changelog
  • 25 - Tenant Authorization Backend Guide
Home
Core APITenant APISupport CenterChangelog
Home
Core APITenant APISupport CenterChangelog
Github
Instagram
|
🇮🇩 Indonesian
  • 🇮🇩 Indonesian
  • 🇺🇸 English
🇮🇩 Indonesian
  • 🇮🇩 Indonesian
  • 🇺🇸 English
  1. Home

10 - Operations Runbook

Runbook singkat untuk operasi harian setelah refactor context-based.

1. Runtime Verification#

cek health route framework: /up
cek route API aktif:
cek schedule:
cek queue worker (wajib untuk provisioning async):

2. Database Lifecycle#

Fresh environment#

Urutan command:
1.
migrasi central (database/migrations/central)
2.
seed cluster registry minimal
3.
migrasi tenant cluster (clusters:migrate)
4.
seed central data

Seeder Notes#

Pastikan tenant seed berjalan setelah migrasi tenant tables tersedia.

3. Auth/Billing Incident Triage#

cek log API terstruktur di log channel aktif
cari pola 401/403 spike pada endpoint auth/tenant
cek webhook billing failure per provider
verifikasi token ability mismatch dan tenant context mismatch
untuk provisioning tenant gagal:
cek log key tenancy.taxonomy.provision_failed
re-run tenant provisioning manual
verifikasi data tenant DB setelah re-run
Referensi komponen:
app/Logging/StructuredApiLogger.php
app/Services/Central/Billing/PaymentWebhookService.php
app/Http/Middleware/Tenant/Context/*
app/Services/Central/Tenancy/Provisioning/TenantProvisioningOrchestrator.php

4. Tenant Provisioning Recovery#

Per tenant:
Checklist setelah re-run:
command exit success
summary created/updated masuk akal
data tenant di cluster sesuai ekspektasi
tidak ada warning provisioning berulang di log

5. Change Management#

Setiap perubahan arsitektur wajib update:
docs/01-project-structure.md
docs/02-context-boundaries.md
dokumen domain terkait (auth/billing/tenant runtime)

6. Archive Policy#

Dokumen lama jangan dihapus langsung; pindahkan ke:
docs/archived/<tanggal>-<label>/
Agar histori desain tetap bisa ditelusuri saat incident review.
Diubah pada 2026-03-03 22:25:30
Sebelumnya
09 - Testing and Quality Gates
Berikutnya
11 - Architecture Decisions (ADR Ringkas)
Built with