-
Notifications
You must be signed in to change notification settings - Fork 425
Enable Smoke Pi safeoutputs CLI mounting and migrate 20 non-smoke workflows to Pi #40375
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.
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
Changes from all commits
a15d3db
11744e6
cda969a
f6eb14b
dd3a355
6bf8621
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Large diffs are not rendered by default.
Large diffs are not rendered by default.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
[/zoom-out] Migrating 20 non-smoke workflows to an
experimentalengine in a single PR is a meaningful blast radius. Pi setsGH_AW_INFO_FIREWALL_ENABLED: falseandGH_AW_INFO_AWF_VERSION: ""in compiled lock files, meaning all migrated workflows run without the AWF firewall container stack — a significant security posture change compared to Copilot.No blocking issue if this is intentional policy for Pi, but worth confirming explicitly in the PR description or a follow-up ADR so reviewers don't have to infer it from the lock file diffs.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Acknowledged — the Pi firewall posture gap was unintentional. Fixed in
6bf8621by addingenableFirewallByDefaultForPi(matching the pattern ofenableFirewallByDefaultForCopilotandenableFirewallByDefaultForClaude). All Pi workflows withsandbox: agent: awfnow getGH_AW_INFO_FIREWALL_ENABLED: "true"and the AWF firewall stack, putting them on the same security posture as Copilot and Claude workflows.