Fleet Devops Iac

Script Patterns

Every script must:

1. set -euo pipefail — fail hard on errors
2. Be idempotent — running twice produces the same result
3. Check dependencies — install or error if missing
4. Use color output — GREEN for success, YELLOW for skip, RED for error
5. Accept arguments — ./script.sh [specific-target] or all by default
6. Source .env — source "$FLEET_DIR/.env" 2>/dev/null || true

Fleet script structure:

#!/usr/bin/env bash
set -euo pipefail

FLEET_DIR="$(cd "$(dirname "$0")/.." && pwd)"
source "$FLEET_DIR/.env" 2>/dev/null || true

GREEN='\033[0;32m'
YELLOW='\033[1;33m'
RED='\033[0;31m'
NC='\033[0m'

# ... idempotent operations ...

Resolve vs hardcode:

• Never hardcode paths — use $FLEET_DIR, $VENV
• Never hardcode agent names — read from config YAML
• Never hardcode URLs — read from .env
• Always use {{placeholders}} in templates, resolve at deploy time

Fleet Infrastructure Map

Contribution: deployment_manifest

When another agent's task needs infrastructure input:

1. Call devops_deployment_contribution(task_id) — gathers phase context
2. Produce a manifest covering:
   • Environment: services, ports, resources
   • Configuration: env vars, secrets, feature flags
   • Deploy strategy: rolling/blue-green/canary
   • Monitoring: what to monitor, alert thresholds
   • Rollback: how to roll back safely, tested procedure
3. Deliver: fleet_contribute(task_id, "deployment_manifest", manifest)

Group Calls

Vendor Patches

Fleet patches are in patches/ and applied by scripts/apply-patches.sh. Patches survive git clone of the vendor repo. When the vendor updates, check if patches are still needed.

Current patches:

• 0001: skills marketplace category/risk upsert fix
• 0002: TOOLS.md parser handles markdown format
• 0003: last_seen_at set on provision complete