docs: establish core infrastructure policies (F1-2)
- Added issue-schema.md (YAML frontmatter, deduplication rules) - Added change-management.md (Git-only changes, version pinning) - Added backup-policy.md (RPO/RTO targets, mandatory restore-drill) - Added secret-policy.md (Vaultwarden only, 90-day rotation, no secrets in Git)
This commit is contained in:
1 parent
694912984a
commit
eee86a73e5
4 files changed
+66
-4
No files matched your search
@@ -1 +1,13 @@
|
|||||||
# Backup Policy
|
#Politica rezervnogo kopirovaniya (Backup Policy)
|
||||||
|
|
||||||
|
## 1. Tselevye pokazateli
|
||||||
|
- RPO: <= 24 chasov.
|
||||||
|
- RTO: <= 4 chasova.
|
||||||
|
|
||||||
|
## 2. Raspisanie bekapov
|
||||||
|
- Ejednevno: pg_dump vseh kriticheskix BD + exsport workflow n8n -> kommit v Git.
|
||||||
|
- Ejenedel'no: vzdump Kriticheskix konteinerov (CT 104, 108, 140, 151).
|
||||||
|
|
||||||
|
## 3. Pravilo Restore-Drill
|
||||||
|
¦ Bekap bez proverki vosstanovleniya ne sushestvuet.
|
||||||
|
- Ejenedelno: avtomaticheskiy restore-drill BD v sandbox-okruzhenii.
|
||||||
@@ -1 +1,16 @@
|
|||||||
# Change Management Policy
|
#Politica upravleniya izmeneniyami (Change Management Policy)
|
||||||
|
|
||||||
|
## 1. Princip "Vsă kak kod"
|
||||||
|
Lyuboe izmenenie v production-srede doljnobyt{ byt' otrazheno v Git-repozitorii `buryan-infra` Net v Git = ne sushestvuet.
|
||||||
|
|
||||||
|
## 2. Zapret ruchnyh pravok
|
||||||
|
Ruchnoe izmenenie konfiguratsii, BD ili konteinerov v obhod runbook strogo zapresheno.
|
||||||
|
|
||||||
|
## 3. Process izmeneniy (type:change)
|
||||||
|
Lyuboe izmenenie doljno byt' oformleno kak zadacha `type:change` i soderzhat':
|
||||||
|
1. Ssylka na kommit v Git.
|
||||||
|
2. Porhagovyi runbook primeneniy.
|
||||||
|
3. Plan otkata (rollback plan).
|
||||||
|
|
||||||
|
## 4. Pinning versii
|
||||||
|
Ispolzovanie tega `latest` dly obrazov Docker zapresheno. Vse versii doljny byt' yvno zafiksirovany.
|
||||||
@@ -1 +1,25 @@
|
|||||||
# Issue Schema Policy
|
#Politica sxem zadach (Issue Schema Policy)
|
||||||
|
|
||||||
|
## 1. Obyazatel'nyi YAML Frontmatter
|
||||||
|
Kajdaa zadacha v Gitea dolzhna nachnat'sy s bloka:
|
||||||
|
```yaml
|
||||||
|
---
|
||||||
|
service: <imy_servisa>
|
||||||
|
ct: <ID_konteinera_ili_IP>
|
||||||
|
symptom_key: <domen>+<monitor>+<tip_alerta>
|
||||||
|
detected_by: <im_agenta_ili_sistemy>
|
||||||
|
runbook: <ssylka_na_runbook_ili_NONE>
|
||||||
|
---
|
||||||
|
```
|
||||||
|
|
||||||
|
## 2. Obyazateln'yye metki (Labels)
|
||||||
|
- `domain:*` (automation, data, comms, edge, identity, observability, knowledge)
|
||||||
|
- `type:` (incident, change, task, audit)
|
||||||
|
- `sev:` (1-Critical, 2-High, 3-Medium, 4-Low)
|
||||||
|
- `agent:*` (imya otvetstvennogo agenta)
|
||||||
|
|
||||||
|
## 3. Pravilo deduplikacii
|
||||||
|
Iorvtornyi alert s tem zhe symptom_key pri otkrytom incidente ne sozdaet novuz zadachu.
|
||||||
|
|
||||||
|
## 4. Zapret na spam
|
||||||
|
Zadachi s neraskrytymi shablonami ili bez symptom_key avtomaticheski zakryvayutsy s metkoi `auto:spam`.
|
||||||
@@ -1 +1,12 @@
|
|||||||
# Secret Policy
|
#Politica raboty s sekretami (Secret Policy)
|
||||||
|
|
||||||
|
## 1. Zapret na hranenie v kode
|
||||||
|
Strogij zapret na hranenie parolei, tokenov API i privatnyh klychei v Git-repozitorii ili JSON-failax workflow n8n.
|
||||||
|
|
||||||
|
## 2. Edinoe hranilishe
|
||||||
|
Vse sekrety dolzny hranitysa iskluchitelyno v Vaultwarden.
|
||||||
|
|
||||||
|
## 3. Rotatsyya i otzyv
|
||||||
|
- Planovaya rotatsyya vseh sekretov: kajdye 90 dney.
|
||||||
|
- Pri podozritel'noi aktivnosti: nemedlennyj otzyv (revoke).
|
||||||
|
- Starye sekrety pomechaeutsya kak [ROTATED] v ops/secrets-master-catalog.sh.
|
||||||
Reference in new issue
Block a user