Skip to content

fix(daily-security-observability): pre-download firewall runs to avoid MCP tool timeout #48988

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
pelikhan merged 2 commits into from
Jul 29, 2026
Merged

fix(daily-security-observability): pre-download firewall runs to avoid MCP tool timeout #48988

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
767fad5
Initial plan
Copilot Jul 29, 2026
19a66ff
fix: pre-download firewall-enabled runs to avoid MCP tool timeout in …
Copilot Jul 29, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 6 additions & 2 deletions .github/workflows/daily-security-observability.lock.yml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

36 changes: 26 additions & 10 deletions .github/workflows/daily-security-observability.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -114,6 +114,31 @@ steps:
}
}' > "$CACHE_FILE"

- name: Download firewall-enabled workflow runs
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: |
mkdir -p /tmp/gh-aw/agent/firewall
FIREWALL_RUNS=/tmp/gh-aw/agent/firewall/firewall-enabled-runs.json
EMPTY_DATA='{"runs":[],"summary":{"total_runs":0}}'

# Download logs filtered to only runs with the firewall feature enabled.
# --artifacts activation: only download the activation artifact (aw_info.json)
# needed for firewall detection, avoiding large agent artifact downloads.
# --timeout 8: cap execution at 8 minutes to prevent runaway downloads.
gh aw logs --firewall --start-date -7d --json -c 100 \
--artifacts activation --timeout 8 \
> "$FIREWALL_RUNS" || true
Comment on lines +129 to +131

# Validate JSON output and fall back to an empty dataset on failure
if ! jq -e '.runs' "$FIREWALL_RUNS" > /dev/null 2>&1; then
echo "No valid firewall logs produced; continuing with empty dataset"
echo "$EMPTY_DATA" > "$FIREWALL_RUNS"
fi

count=$(jq '.runs | length' "$FIREWALL_RUNS" 2>/dev/null || echo 0)
echo "Downloaded $count firewall-enabled workflow runs"

tools:
bash:
- "*"
Expand Down Expand Up @@ -174,16 +199,7 @@ Both datasets cover the **last 7 days** and share the cache-memory path `/tmp/gh

**ALWAYS PERFORM FRESH ANALYSIS**: This report must always use fresh data from the audit tool. Do NOT skip analysis based on cached results or reuse aggregated statistics from previous runs.

Use the `logs` tool from the agentic-workflows MCP server to collect workflow runs that have firewall enabled:

**Tool call:**
```json
{
"firewall": true,
"start_date": "-7d",
"count": 100
}
```
Read the pre-downloaded list of firewall-enabled workflow runs from `/tmp/gh-aw/agent/firewall/firewall-enabled-runs.json`. This file was populated by the startup step and contains runs from the last 7 days with the firewall feature enabled. Extract the `run_id` from each entry in the `runs` array.

### Step 1.2: Early Exit if No Firewall Data

Expand Down