Add Context API launch content: announcement blog post and public docs - #21059
Draft
lblackstone wants to merge 2 commits into
Draft
Add Context API launch content: announcement blog post and public docs#21059lblackstone wants to merge 2 commits into
lblackstone wants to merge 2 commits into
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Contributor
Social Media Reviewcontent/blog/pulumi-context-api/index.mdX — PASSLinkedIn — PASSBluesky — PASSNote: social card not reachable ( Updated for commit |
Collaborator
|
Your site preview for commit 8760d74 is ready! 🎉 http://www-testing-pulumi-docs-origin-pr-21059-8760d745.s3-website.us-west-2.amazonaws.com Changed pages: |
cnunciato
self-requested a review
August 21, 2026 21:26
New docs section at /docs/insights/context-api/: - Overview page: concept-level graph model, both endpoints in CLI and curl form, the fetch-the-primer workflow, and a copy-pasteable AGENTS.md/CLAUDE.md snippet for agent onboarding. The primer the API serves stays the canonical query-language reference; the docs site deliberately doesn't mirror it. - Query recipes page: six selectors adapted from the service's test-pinned cookbook, each with its example response (from the matching golden files) collapsed under the query. Launch wiring: context-api pricing feature (hidden, Enterprise+) for the edition callout, a launch changelog entry, a cross-link card on the AI landing page, and a docs pointer in the announcement blog post outside the primer-only get-started steps. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
lblackstone
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Pulumi Context API launches in preview on 2026-08-26. This PR is the launch content: an announcement blog post plus the public docs (overview, query recipes, a changelog entry, and an
/docs/ai/landing-page card).The API already serves its own always-in-sync reference: the schema endpoint returns a full primer (vocabulary, grammar, worked examples) generated from the live deployment. So the docs' job isn't to mirror that query-language reference, which would just rot against it, but to make the API discoverable and teach the fetch-the-primer workflow. The overview page centers a paste-into-
AGENTS.md/CLAUDE.mdsnippet, since agents are the primary audience; the site's existing markdown and llms.txt outputs pick up the new pages automatically. Human-focused tutorials and a mirrored query-language reference are deliberately out of scope for launch.The recipe selectors and their example responses in
recipes.mdare copied from golden-test-pinned fixtures in the service repo, so they're provably correct as of writing.The Context API is Enterprise+ (
data/pulumi_pricing.yaml, new hiddencontext-apifeature entry driving the edition callout), but it reuses Resource Search's permission model, which starts at the Team edition. The edition callout and the permission prose are kept as separate statements for that reason, rather than merged into one.🤖 Generated with Claude Code