Skip to content
Episode from the podcast Ship It Weekly - DevOps, SRE, Platform and Cloud Engineering News
GitHub Outage, PleaseFix Agentic Browser Vulnerability, AWS Certificate Manager Drops Email Validation, Cloudflare TypeScript CI Workflows, AI Observability Consolidation, and the Hidden Cost of “Simple” Platform Changes artwork

Episode

GitHub Outage, PleaseFix Agentic Browser Vulnerability, AWS Certificate Manager Drops Email Validation, Cloudflare TypeScript CI Workflows, AI Observability Consolidation, and the Hidden Cost of “Simple” Platform Changes

Released Friday, August 21st 2026 17 min

Show notes

About this episode

This week on Ship It Weekly: GitHub suffers another widespread outage affecting the web interface, APIs, Actions, authentication, Copilot, and other critical developer workflows. Zenity Labs demonstrates PleaseFix attacks against agentic browsers, where malicious content can influence agents with access to authenticated sessions and privileged tools. AWS Certificate Manager is moving away from email validation, and Cloudflare is experimenting with CI pipelines defined as TypeScript instead of YAML. The bigger theme this week is dependencies and boundaries we tend to ignore until something breaks. GitHub is no longer just where the code lives. Agentic browsers are no longer just displaying webpages. Certificate renewal is not something you want depending on someone checking an inbox. And CI pipelines have become software systems of their own. Links GitHub Hit by Widespread Outage https://devops.com/github-hit-by-widespread-outage-halting-work-for-global-developers/ Zenity Labs: PleaseFix in Agentic Browsers https://zenity.io/company-overview/newsroom/company-news/zenity-labs-exposes-the-full-scope-of-pleasefix AWS Certificate Manager Ending Email Validation https://aws.amazon.com/blogs/security/aws-certificate-manager-will-discontinue-email-validation-to-prove-domain-validation-for-certificates/ Certificate Expiry Is Still Taking Down Major Platforms https://tokentimer.ch/blog/tls-certificate-expiry-outages Cloudflare Turns CI Pipelines into TypeScript Workflows https://www.infoq.com/news/2026/08/cloudflare-ci-code-workflows/ Dynatrace Acquires Arize https://devops.com/dynatrace-acquires-arize-as-ai-agents-deepen-the-observability-challenge/ AWS Open-Sources Dogwood https://www.infoq.com/news/2026/08/aws-dogwood-agent-policy/ Pulumi v3.258.0 https://github.com/pulumi/pulumi/releases/tag/v3.258.0 AWS Key Breach and Data-Transfer Signal https://assets.theregister.com/2026/08/13/20267/ Mario Saved the EU but Broke My System https://www.uptimelabs.io/articles/hamed-2012-...

More from Ship It Weekly - DevOps, SRE, Platform and Cloud Engineering News

All episodes

Java4Shell OpenJDK Flaw, Microsoft Agent Framework PyPI Package Hijacked, Confluence Axis RCE Exploited & FAA Ground Stop Traced to a Router

18 min

This week on Ship It Weekly, Java4Shell: a memory bug in the OpenJDK HotSpot JVM's Base64 decoder, fixed Tuesday, that only bites on x86 CPUs with AVX-512 VBMI. Microsoft's agent-framework package on PyPI shipped a credential stealer in two versions that were live for under an hour. Attackers are exploiting Confluence Data Center through CVE-2026-90436, a bug in its old Apache Axis SOAP library, and in one case reached Microsoft 365 in about twelve hours. And the FAA's preliminary cause for last Friday's nationwide ground stop: a new router at a remote site that flooded its network. The thread: the layer under the code. A CPU instruction set, a .pth file that runs before your code does, a 20-year-old SOAP library, and a router swap logged on paper. In the lightning round: wfx-loot, the GitHub campaign that probed 61,764 repos; PHP's second emergency release in a month; and kube-proxy's IPVS mode leaving Kubernetes in 1.40. The human closer: Oakley Hall on why your RCAs aren't working. Documents without data, and systemic fixes handed to whichever team hit them first. Ship It Weekly turns one today. Thank you for listening. The show is a 2026 DevOps Dozen finalist for Best DevOps Community Program or Event, and I'm one for Enterprise DevOps Champion of the Year. Voting is open through December 31. Highlights • Check /proc/cpuinfo for avx512vbmi, and the JVM flag that closes the path • Pin agent-framework 1.26.0 and search for 1.26.1 and 1.26.2 • Is Confluence's Remote API on? Where to check, and the fixed version • How a router swap in Arkansas stopped flights across the country • A corrective action needs an owner who can finish it Links OpenJDK advisory, November 17 Java4Shell and the workaround flag (Wiz) Java4Shell severity and exploitation (Help Net Security) Malicious agent-framework versions on PyPI (Wiz) Confluence Data Center and N-central exploited (Rapid7) Ground stop questions and answers (FAA) FAA ground stop traced to a telecom issue (FedScoop) wfx-loot...

Ship It Conversations: Ted Julian of Flux on the AI Code Visibility Gap, the Code Review Bottleneck, Measuring What AI Changes, Who Owns AI-Generated Code in Production, Guardrails Before Loops, and Why Disruption Is a Career Opportunity

39 min

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps. In this Ship It Conversations episode, I talk with Ted Julian about the gap between AI-generated code getting written and teams trusting it enough to ship it, why code review is the first thing to break, and who should own AI-generated code once it's running in production. Ted is the founder and CEO of Flux (askflux.ai), an engineering intelligence platform, not Flux CD the GitOps tool. He has spent more than twenty years building security and infrastructure companies, including Resilient Systems, Arbor Networks and @stake. We start with Flux's AI Code Generation Reality Check: 44.7% of the organizations surveyed already run AI-generated code in production, and 35% write it but don't ship it. What holds them back is trust: complexity that could spiral into an outage, a new library with a vulnerability, regulated data nobody has really scrutinized. Ted calls code review act two of an AI transformation, and he says it's a people problem as much as a tooling problem. His once-in-a-career hack: measure features versus maintenance versus bug fixes now, backfill it, and show the before and after. At one customer, feature work went from 9% to 43%, and it became a chart in their board meeting. We also get into why engineering has to be the yes squad, with guardrails, the bill that comes due when someone has to understand code nobody really wrote, who feeds the cat, what loops mean for visibility, and why tech disruption is the best career opportunity you'll get. Highlights • Written but not shipped: 44.7% in production, 35% holding back • Code review breaks first, and it's a people problem • Measure features vs. maintenance vs. bug fixes, then backfill • From 9% to 43% feature work, as a board chart • The yes squad, with guardrails • The bill for code nobody really wrote • Who feeds the cat: one owner for AI-generated code • Loops, dark factories and a control plane • Why disruptio...

Ship It Conversations: Tristan Handy of Fivetran + dbt on AI Agents as Data Consumers, Why Dashboards Stop Being the Product, Context Layers, Evals, Operating on the System, Software Factories, and Why Text-to-SQL Isn't the Hard Part

37 min

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps. In this Ship It Conversations episode, I talk with Tristan Handy about what changes when AI agents, not people, become the main consumers of your company's data, why the hard part isn't text-to-SQL, and why he thinks the most interesting work is operating on the system instead of inside it. Tristan is the founder of dbt Labs and president and co-founder of Fivetran. If you've worked anywhere near a data team, you've probably run into dbt. His team likes to call it Terraform for data. Correction: Tristan's title changed after we recorded. He is now the founder of dbt Labs and president and co-founder of Fivetran. We start with his line that dashboards are a hack for the human visual cortex. As agents take over the pattern-finding, the asset moves down the stack: a well-modeled gold layer, a semantic layer that captures how your organization calculates its metrics, and a context store that helps the agent make sense of all of it. On reliability, Tristan says agents already write SQL that compiles and runs almost every time. The hard part is whether they understood the question and the business behind it. In the benchmarks he's seen, an agent turned loose on raw enterprise data gets about 30% of its answers semantically right. Give it context and a semantic layer, and it's north of 90%. We also get into where autonomy should stop once agents can act on data, why analytics engineers (and SREs) should be operating on the system rather than inside it, how dbt earned practitioners' trust, what he got wrong selling to enterprises, and where dbt draws its open source line after the Fivetran merger. His first step for a platform or data team is to eat your spinach: a well-governed data lake, well-modeled data and a semantic layer, then a context layer and evals. And his team paused dbt 2 work for two months to build an agent loop that took conformance from about 45% to 93%. Highlight...

AWS Roles Trusting Qubole Abused to Steal Secrets, Claude Code's Don't Ask Again File Leaks Credentials, KubeCon Agent Sandboxes for Kubernetes & WorkOS Breach Traced to an AI Agent

15 min

This week on Ship It Weekly, an attacker used Qubole's trusted access into customer AWS accounts to read secrets and pull whole S3 buckets. Claude Code's "don't ask again" button has been saving passwords and API keys into .claude/settings.local.json, a file that keeps turning up on GitHub and Docker Hub. At KubeCon, the CNCF took in Agent Substrate and OpenShell as Sandbox projects, and AWS launched Nitro Sandboxes for EKS. And WorkOS traced a breach of an internal sales tool to a security researcher's AI agent that escaped its test environment. The thread: what can it touch? A vendor role nobody removed, an approval that saved the secret with the command, agents running unreviewed code, and an internet-facing tool with a guessable dev credential. In the lightning round: an exploited Outlook bug (CVE-2026-124194) and a 9.9 Azure DevOps Server RCE in Patch Tuesday, N-able patching the Able2Shell exploits in N-central, KubeVirt's CNCF graduation, and OpenShift 5 going GA. The human closer comes from Brent Chapman: incident resolution time isn't something you should target. Target what you can change, and track the rest. Ship It Weekly is a 2026 DevOps Dozen finalist for Best DevOps Community Program or Event, and I'm a finalist for Enterprise DevOps Champion of the Year. The public vote is open through December 31. Highlights • Why the External ID didn't stop a stolen vendor credential • Find every role that trusts an outside account, and delete the idle ones • settings.local.json: rotate, untrack, and add it to .dockerignore • Moving an agent's boundary off the shared kernel • WorkOS's own list: internet-facing API, dev credential, no rate limit • Target the steps you control, not resolution time Links Qubole cross-account access abused (Wiz) Claude Code's "don't ask again" file leaks secrets (The Hacker News) settings.local.json secrets on GitHub and Docker Hub (GitGuardian) Agent Substrate and OpenShell join the CNCF Nitro Sandboxes for Amazon EKS (AWS) WorkOS inc...

Ship It Conversations: Mallory Haigh of PlatformEngineering.org on Why Context Isn't Enough for AI Agents, Harness and Governance, Probabilistic and Hybrid Paths, Agent Identity, and Building Platform Trust Before Agents

39 min

This is a guest conversation episode of Ship It Weekly, separate from the weekly news recaps. In this Ship It Conversations episode, I talk with Mallory Haigh about why context alone isn't enough for AI agents, the harness and governance layers that actually run them, and why she tells some platform teams to pump the brakes before adding agents at all. Mallory is Head of Platform Education and Advocacy at PlatformEngineering.org. She teaches in Platform Engineering University and coaches platform teams through Platform Engineering Consulting, where the job gets jokingly called "platform therapist". We start with her New York City analogy. Drop someone in the middle of the city with no directions and they'll get lost, and an agents.md file on its own does the same to an agent. It also needs to know what to do, how to do it, how it'll know it's done, and what it's allowed to touch. Mallory splits that into the harness, which is how the agent does the work, and governance: who and what is allowed, what's safe, and how it's watched. Then we get into IDPs as context layers. Mallory says that's partly right, because the IDP and its golden paths are the foundation. What's missing are path specifications. Probabilistic paths are agent-driven, like a read-only PR review. Deterministic paths are your pipelines, like a CI build. Hybrid paths pair an agent with a gate: the agent opens the PR, CI validates it, the agent retries, and a human makes the final call. Cap those retries at three to five, and if an agent always does the same thing with the same outcome, ask whether it should be an agent at all. On governance, Mallory says platform engineering is a practice about building trust, and that in the last three weeks alone she's told multiple platform teams to pump the brakes on agents because they can't get human governance right yet. We cover agent identity (specialists, not generalists, built on the RBAC you already have), agents watching terabytes of logs a day for SRE tea...

This podcast, its content and its artwork are not owned by, affiliated with, or endorsed by Castquire.

Up next

  1. Nothing queued. Use + Queue on any episode to line it up.

0:00 0:00