Update CrossGuard references to Pulumi Policies by CamSoper · Pull Request #19185 · pulumi/docs

CamSoper · 2026-05-19T19:03:54Z

Proposed changes

Updates documentation references from "Pulumi CrossGuard" to "Pulumi Policies" across two content files:

what-is-cloud-infrastructure-autoscaling.md: Updates 2 references to CrossGuard in the Pulumi section and cost management discussion
what-is-devops.md: Updates 2 references to CrossGuard in the policy as code section and DevOps toolchain table

Also updates the author attribution for the autoscaling article from "zack-chase" to "cam-soper".

These changes reflect the product naming update from CrossGuard to Pulumi Policies while maintaining all existing links and context.

https://claude.ai/code/session_018i6G5f7SLFcWAmHnaPj1Sq

… Is pages Set what-is-cloud-infrastructure-autoscaling.md to cam-soper and replace the deprecated "CrossGuard" name with "Pulumi Policies" (keeping the same /docs/insights/policy/ link target) in both that page and what-is-devops.md.

github-actions · 2026-05-19T19:09:51Z

Pre-merge Review — Last updated 2026-05-19T19:06:28Z

Tip

Summary: Two-file terminology refresh in content/what-is/ — replacing the legacy product name "CrossGuard" with "Pulumi Policies" in what-is-cloud-infrastructure-autoscaling.md (two instances) and what-is-devops.md (two instances), and setting authors: ["cam-soper"] on the autoscaling page. The kind of wrongness that would block a reader: an outdated product name they couldn't search the docs for, or a broken policy-docs link target. The link target /docs/insights/policy/ is unchanged and confirmed canonical (the page's title_tag is "Pulumi Policies | Insights & Governance"; legacy /docs/iac/crossguard/-family paths are retained as aliases on that page). Sibling What Is pages — what-is-ci-cd.md, what-is-platform-engineering.md, what-is-pulumi.md, what-is-hipaa.md — already use "Pulumi Policies", so this brings two stragglers in line with the rest of the family. Frontmatter sweep, temporal-trigger sweep, and external claim verification ran; five claims extracted, four verified, one ("author is cam-soper") triaged as mis-sourced (the value is observable in the changed frontmatter, and data/team/team/cam-soper.toml exists).

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	HIGH

Investigation log

Cross-sibling reads: not run (not in a templated section)
External claim verification: 4 of 5 claims verified (1 unverifiable, 0 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 4 Pass 1, 0 Pass 2, 1 Pass 3 (verified 0, contradicted 0, unverifiable 1).
Cited-claim spot-checks: not run (no cited claims)
Frontmatter sweep: ran on body + meta_desc
Temporal-trigger sweep: ran (recency words present in diff; spot-check in-review)
Code execution: not run (no static/programs/ change)
Code-examples checks: not run (no fenced code blocks in content files)
Editorial-balance pass: not run (not under content/blog/)

🚨 Outstanding	⚠️ Low-confidence	💡 Pre-existing	✅ Resolved
0	0	0	0

🔍 Verification trail

5 claims extracted · 4 verified · 1 unverifiable · 0 contradicted

L30 in content/what-is/what-is-cloud-infrastructure-autoscaling.md "The author of the article 'What is Cloud Infrastructure Autoscaling' is cam-soper." → 🤷 unverifiable (evidence: Web searches returned the rendered page content and GitHub repo landing pages, but no source showing the frontmatter author field of content/what-is/what-is-cloud-infrastructure-autoscaling.md. The file's author metadata is only access…; source: WebSearch ran query "pulumi/docs what-is-cloud-infrastructure-autoscaling cam-soper author frontmatter"; top results didn't address the claim)
L134 in content/what-is/what-is-cloud-infrastructure-autoscaling.md "Pulumi Policies (at /docs/insights/policy/) can enforce scaling guardrails such as 'every production ASG must have a non-zero max,' 'no ASG without scale-in pr…" (also L174) → ✅ verified (framing: strengthened — the policy docs describe general guardrail capability; the claim narrows this to specific autoscaling guardrail examples, which are a valid subs…; evidence: The path /docs/insights/policy/ exists in the repo at content/docs/insights/policy/_index.md and describes Pulumi Policies as a policy-as-code system that "enables you to implement policy as code across your entire cloud infrastructure…; source: repo:content/docs/insights/policy/_index.md)
L174 in content/what-is/what-is-cloud-infrastructure-autoscaling.md "Pulumi Policies (at /docs/insights/policy/) can be used in IaC to enforce a maximum on every ASG / MIG / scale set / HPA." → ✅ verified (evidence: The path /docs/insights/policy/ exists and resolves to the Pulumi Policies documentation page, which confirms policies can enforce infrastructure compliance rules in IaC, including cost-control guardrails like "Set spending limits" and p…; source: repo:content/docs/insights/policy/_index.md)
L109 in content/what-is/what-is-devops.md "The Pulumi policy-as-code product is named 'Pulumi Policies' (not 'Pulumi CrossGuard'), and its documentation lives at /docs/insights/policy/." (also L150) → ✅ verified (evidence: The content/docs/insights/policy/_index.md file has title_tag: "Pulumi Policies | Insights & Governance" and body text "Pulumi Policies enables you to implement policy as code across your entire cloud infrastructure." The old "CrossGua…; source: repo:content/docs/insights/policy/_index.md)
L150 in content/what-is/what-is-devops.md "Pulumi Policies is a policy-as-code tool (listed under the 'Policy as code' category alongside Open Policy Agent and HashiCorp Sentinel)." → ✅ verified (evidence: The /docs/insights/policy/ page (Pulumi Policies) explicitly describes itself as a policy-as-code tool: "Pulumi Policies enables you to implement policy as code across your entire cloud infrastructure." The page also references OPA (Open…; source: content/docs/insights/policy/_index.md)

🚨 Outstanding in this PR

No outstanding findings in this PR.

⚠️ Low-confidence

No low-confidence findings in this PR.

📋 Triaged verifier findings

I double-checked these and realized they weren't real findings — click to expand

[L30] content/what-is/what-is-cloud-infrastructure-autoscaling.md — "The author of the article 'What is Cloud Infrastructure Autoscaling' is cam-soper." — Mis-sourced: the verifier ran a WebSearch instead of reading the frontmatter of the file being changed. Direct evidence: line 30 of the changed file is authors: ["cam-soper"], and data/team/team/cam-soper.toml exists as the author profile. This is the assignment the PR is making — it's directly observable, not a web claim.

💡 Pre-existing issues in touched files (optional)

No pre-existing issues in touched files.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

2026-05-19T19:06:28Z — Brings two What Is pages in line with the rest of the family: CrossGuard → Pulumi Policies (+5/−5) and assigns cam-soper as author of the autoscaling page; no blockers. (64c477f)

Need a re-review? Want to dispute a finding? Mention @claude and include #update-review.
(For ad-hoc questions or fixes, just @claude — no hashtag.)

pulumi-bot · 2026-05-19T19:14:36Z

Your site preview for commit 64c477f is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19185-64c477fa.s3-website.us-west-2.amazonaws.com

@claude

* ci(docs-review): broaden Vale/URL-fetch path filter to what-is, tutorials, learn The Vale step and URL pre-fetch step were gated to `content/(docs|blog)/`, which silently skipped every PR under `content/what-is/`, `content/tutorials/`, and `content/learn/`. That captured nearly every content PR landed since the 2026-05-15 pipeline overhaul — the explainer rewrites alone (#19141–#19153, #19185) all touched only `content/what-is/`, so Vale never ran on them and no Style findings appeared in their pinned reviews. Broaden the regex to `^content/(docs|blog|what-is|tutorials|learn)/.*\.md$` in all five filter sites: - .github/workflows/claude-code-review.yml (Vale + URL pre-fetch) - .github/workflows/claude-triage.yml (Vale in triage) - .github/workflows/claude-update.yml (Vale on @claude #update-review) - extract-urls-and-fetch.py (Python regex must match the workflow filter) `content/learn/` doesn't exist yet but is included for forward compatibility — `triage-classify.py:32` already classifies it as `domain:docs` alongside docs/tutorials/what-is, so this keeps the path-filter scope consistent with the domain classifier. Editorial-balance (blog-only), cross-sibling discovery (docs-only), and the social-review workflow stay narrow by design — those checks target specific content shapes, not all prose. `.vale.ini` per-path overrides are unchanged: the `Google.FirstPerson` exemption is blog-only because blog posts are written in author voice; what-is/tutorials/learn use institutional voice and should still flag first-person. Also update echo messages and one comment in validate-pinned.py that referenced the old "docs/blog" scope. Co-Authored-By: Claude <noreply@anthropic.com> https://claude.ai/code/session_01KAPbBaLgeuNWmLwU4ARASQ * Drop `learn` path from Vale scope filter in claude-update.yml Agent-Logs-Url: https://github.com/pulumi/docs/sessions/43591091-fb4f-44cd-8d9a-9eea988b42be Co-authored-by: CamSoper <137648+CamSoper@users.noreply.github.com> * Apply suggestion from @CamSoper --------- Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: CamSoper <137648+CamSoper@users.noreply.github.com>

CamSoper temporarily deployed to testing May 19, 2026 19:04 — with GitHub Actions Inactive

github-actions Bot added the review:triaging Claude Triage is currently classifying the PR label May 19, 2026

CamSoper requested a review from alexleventer May 19, 2026 19:04

github-actions Bot added domain:docs PR touches technical docs and removed review:triaging Claude Triage is currently classifying the PR labels May 19, 2026

CamSoper requested a review from sicarul May 19, 2026 19:05

github-actions Bot added the review:in-progress Claude review is currently running label May 19, 2026

CamSoper enabled auto-merge (squash) May 19, 2026 19:05

github-actions Bot added review:no-blockers Claude review completed cleanly; outstanding is empty and removed review:in-progress Claude review is currently running labels May 19, 2026

alexleventer approved these changes May 19, 2026

View reviewed changes

CamSoper merged commit 86de211 into master May 19, 2026
9 checks passed

CamSoper deleted the claude/update-authors-remove-crossguard-BCCyh branch May 19, 2026 19:22

CamSoper temporarily deployed to testing May 19, 2026 19:22 — with GitHub Actions Inactive

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update CrossGuard references to Pulumi Policies#19185

Update CrossGuard references to Pulumi Policies#19185
CamSoper merged 1 commit into
masterfrom
claude/update-authors-remove-crossguard-BCCyh

CamSoper commented May 19, 2026

Uh oh!

github-actions Bot commented May 19, 2026

Uh oh!

pulumi-bot commented May 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

Conversation

CamSoper commented May 19, 2026

Proposed changes

Uh oh!

github-actions Bot commented May 19, 2026

Pre-merge Review — Last updated 2026-05-19T19:06:28Z

🔍 Verification trail

🚨 Outstanding in this PR

⚠️ Low-confidence

📋 Triaged verifier findings

💡 Pre-existing issues in touched files (optional)

✅ Resolved since last review

📜 Review history

Uh oh!

pulumi-bot commented May 19, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants