github-mcp-server-devops/examples/inventory.yaml at main · tsviz/github-mcp-server-devops · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
# Repository Inventory Example
# This file defines which repositories ActionsPulse monitors and analyzes
# Place in: config/repositories/inventory.yaml

apiVersion: devops-observer/v1
kind: RepositoryInventory
metadata:
  name: example-inventory
  version: "1.0.0"
  description: "Example repository inventory for ActionsPulse"

spec:
  # =============================================================================
  # DISCOVERY SETTINGS
  # =============================================================================
  # Auto-discovery of repositories in your organization
  # Set enabled: true to automatically find repositories
  discovery:
    enabled: false              # Manual configuration preferred
    includeArchived: false      # Exclude archived repos
    includeForked: false        # Exclude forked repos
    excludePatterns:            # Patterns to exclude from discovery
      - "*-archived"
      - "legacy-*"
      - "test-*"
      - ".github"

  # =============================================================================
  # REPOSITORY DEFINITIONS
  # =============================================================================
  # Explicitly define which repositories to monitor
  repositories:
    # Tier-1: Production-critical applications
    - name: api-gateway
      team: platform-engineering
      tier: tier-1               # Critical - 99.9% uptime SLA
      compliance:
        - SOC2
        - HIPAA
      owner: my-org              # Optional if using GITHUB_ORG env var
      tags:
        - java
        - springboot
        - production
        - api

    - name: auth-service
      team: security
      tier: tier-1
      compliance:
        - SOC2
        - PCI-DSS
      tags:
        - go
        - authentication
        - production

    # Tier-2: Internal tools and staging
    - name: admin-dashboard
      team: frontend
      tier: tier-2               # Standard - 99% uptime SLA
      compliance:
        - SOC2
      tags:
        - react
        - typescript
        - internal

    - name: data-pipeline
      team: data-engineering
      tier: tier-2
      compliance:
        - SOC2
      tags:
        - python
        - airflow
        - etl

    # Tier-3: Development and experimental
    - name: feature-experiments
      team: innovation
      tier: tier-3               # Low priority - best effort
      tags:
        - experimental
        - development

  # =============================================================================
  # REPOSITORY GROUPS
  # =============================================================================
  # Group repositories for bulk configuration and reporting
  groups:
    # Production services group
    production:
      repositories:
        - api-gateway
        - auth-service
      tier: tier-1
      team: platform-engineering
      compliance:
        - SOC2
        - HIPAA

    # Internal tools group
    internal:
      repositories:
        - admin-dashboard
        - data-pipeline
      tier: tier-2
      team: internal-tools

    # All Java applications
    java-apps:
      repositories:
        - api-gateway
      tags:
        - java

# =============================================================================
# TIER REFERENCE
# =============================================================================
# tier-1: 🔴 Critical
#   - 99.9% uptime SLA
#   - < 15 minute response time
#   - Production, revenue-critical systems
#
# tier-2: 🟡 Standard
#   - 99% uptime SLA
#   - < 1 hour response time
#   - Internal tools, staging environments
#
# tier-3: 🟢 Low Priority
#   - Best effort uptime
#   - < 24 hour response time
#   - Development, experimental projects