Set up DevOps for network automation

# Create a new repo for network automation
gh repo create network-automation --private --description "Network-as-Code configs"
cd network-automation

# Or via web: github.com/new

# Create the standard NAPT repo layout
mkdir -p intent/{production,staging,lab}/{bgp,dc,sdwan,security,compliance}
mkdir -p tests/{routing,fabric,security}
mkdir -p pipelines
mkdir -p inventory
mkdir -p scripts

# Create initial files
cat > .gitignore << 'EOF'
# Never commit credentials
.env
*.key
*.pem
devices.csv     # may contain credentials
secrets.yaml

# Python
__pycache__/
*.pyc
.venv/

# NAPT local cache
.napt/
EOF

cat > README.md << 'EOF'
# Network Automation Repository

Network-as-Code configurations and automation scripts for NAPT.

## Structure
- intent/    YAML intent files by environment and domain
- tests/     Network validation test suites
- pipelines/ NAPT pipeline definitions (exported JSON)
- inventory/ Device inventory (credentials via NAPT Vault, not here)
- scripts/   Custom Python scripts
EOF

git init && git add . && git commit -m "init: NAPT network automation repo"

# Network Intent: Edge BGP Peers — Staging
# Owner: network-team
# Last updated: 2026-06-16

apiVersion: napt.networkgig.in/v1
kind: BGPPeer
metadata:
  name: edge-rtr01-transit-a
  namespace: staging
  labels:
    site: mumbai-dc1
    role: edge
    vendor: cisco_xr
    team: network-ops
spec:
  localAs: 65000
  neighbor: 10.255.0.1        # staging test peer IP
  remoteAs: 65001
  description: "Staging transit simulation peer"
  addressFamily:
    ipv4Unicast: true
  policy:
    inbound: STAGING-TRANSIT-IN
    outbound: STAGING-TRANSIT-OUT
  security:
    ttlSecurity: 1
  maxPrefix:
    limit: 10000
    restartInterval: 5

git add intent/staging/bgp/edge-peers.yaml
git commit -m "feat(bgp/staging): add transit simulation peer on edge-rtr01"
git push origin main

npm install -g @networkgig/napt-mcp

{
  "mcpServers": {
    "napt": {
      "command": "npx",
      "args": ["-y", "@networkgig/napt-mcp"],
      "env": {
        "NAPT_API_KEY": "napt_mcp_your_key_here",
        "NAPT_WORKSPACE": "your_workspace_id_here"
      }
    }
  }
}

{
  "mcpServers": {
    "napt": {
      "command": "npx",
      "args": ["-y", "@networkgig/napt-mcp"],
      "env": { "NAPT_API_KEY": "napt_mcp_your_key_here" }
    }
  }
}

name: NAPT Network Validation

on:
  push:
    paths:
      - 'intent/**'
  pull_request:
    paths:
      - 'intent/**'

jobs:
  validate:
    runs-on: ubuntu-latest
    name: Validate network intent files

    steps:
      - name: Checkout code
        uses: actions/checkout@v4

      - name: Set up Python
        uses: actions/setup-python@v5
        with:
          python-version: '3.11'

      - name: Install NAPT CLI
        run: pip install napt-cli    # NAPT's Python CLI (coming soon)

      - name: Validate intent files
        env:
          NAPT_API_KEY: ${{ secrets.NAPT_API_KEY }}
        run: |
          napt validate intent/      # Schema validation via NAPT API

      - name: Run NAPT dry-run
        if: github.ref == 'refs/heads/main'
        env:
          NAPT_API_KEY: ${{ secrets.NAPT_API_KEY }}
          SSH_PASS: ${{ secrets.SSH_PASS }}
        run: |
          napt run --pipeline "Staging BGP Change Pipeline" --dry-run

      - name: Post results to PR
        if: github.event_name == 'pull_request'
        uses: actions/github-script@v7
        with:
          script: |
            // Post NAPT pipeline results as PR comment
            // (handled by NAPT's PR comment bot if Git integration is connected)