git:20260911.3a0a7c8 to git:20260911.94f82ba

25 added, 0 removed. Audit A to A.

---

name: "cicd-infra-discover"

description: "Generate cloud resource discovery script for IaC import"

---

+ ## Codex harness adaptations

+ Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:

+ - `CLAUDE.md` references: Codex reads `AGENTS.md`; treat them as the target repo's agent-context file.

# /cicd-infra-discover - Cloud Resource Discovery

Generate a discovery script that audits existing cloud resources and outputs them in a format suitable for IaC import (`terraform import`, etc.).

+ ## Step 1: Locate CPP Source

+ ```bash

+ CPP_DIR=""

+ for dir in ~/Projects/claude-power-pack /opt/claude-power-pack ~/.claude-power-pack; do

+ if [ -d "$dir" ] && [ -f "$dir/CLAUDE.md" ]; then

+ CPP_DIR="$dir"

+ break

+ fi

+ done

+ if [ -z "$CPP_DIR" ]; then

+ echo "ERROR: claude-power-pack not found"

+ exit 1

+ fi

+ ```

+ ---

## Instructions

1. **Detect cloud provider** from `.claude/cicd.yml` or ask the user (aws/azure/gcp).

2. **Generate the discovery script:**

```bash

PYTHONPATH="$CPP_DIR:$PYTHONPATH" uv run --project "$CPP_DIR" python -m lib.cicd infra-discover --path "$(pwd)" --cloud aws --write

```

3. **Optionally run the script** if the user has CLI tools configured:

```bash

bash infra/scripts/discover-aws.sh

```

4. **Report findings** and suggest which resources to import first (most critical/fragile).

## When to Use

- Starting IaC from scratch ("no documentation exists yet")

- Auditing what exists before codifying it

- Building a manifest for `terraform import`

## Key Principle

Even if you only plan to run infrastructure changes once, codify them. The value is having an executable runbook, not a stale wiki page.

## Related

- `/cicd-infra-init` - Scaffold IaC directory structure

- `/cicd-infra-pipeline` - Generate CI/CD pipelines with approval gates