Merge branch 'master' into gads-categories

Author: asafashirov

.devcontainer/devcontainer.json

@@ -1,7 +1,10 @@
 {
 	"name": "Pulumi Docs Author Environment",
-	"image": "mcr.microsoft.com/devcontainers/typescript-node:1-22-bookworm",
+	"image": "mcr.microsoft.com/devcontainers/base:trixie",
 	"features": {
+		"ghcr.io/devcontainers/features/node:1": {
+			"version": "22"
+		},
 		"ghcr.io/devcontainers/features/dotnet:2": {
 			"version": "lts"
 		},
@@ -13,7 +16,7 @@
 		},
 		"ghcr.io/devcontainers/features/python:1": {
 			"installTools": true,
-			"version": "latest"
+			"version": "os-provided"
 		},
 		"ghcr.io/devcontainers/features/github-cli:1": {
 			"installDirectlyFromGitHubRelease": true,
@@ -31,6 +34,5 @@
 			]
 		}
 	},
-
-	"postCreateCommand":  "./.devcontainer/scripts/post-create.sh"
-}
+	"postCreateCommand": "./.devcontainer/scripts/post-create.sh"
+}

.devcontainer/scripts/post-create.sh

@@ -11,9 +11,13 @@ curl -fsSL https://packages.cloud.google.com/apt/doc/apt-key.gpg \
 sudo apt-get update -y
 sudo apt-get install -y google-cloud-cli
 
+# Install TypeScript
+npm install -g typescript
 
+# Install Pulumi CLI
 curl -fsSL https://get.pulumi.com | sh
 echo 'export PATH=$HOME/.pulumi/bin:$PATH' >> ~/.bashrc
 echo 'export PATH=$HOME/.pulumi/bin:$PATH' >> ~/.profile
 export PATH=$HOME/.pulumi/bin:$PATH
 pulumi version
+

content/blog/cli-ai-extensions/index.md

@@ -18,6 +18,10 @@ social:
     linkedin: "Excited to announce AI-powered features in the Pulumi CLI! ✨ Our new 'explain' feature translates complex infrastructure changes into clear, human-readable summaries, while our AI error analysis transforms cryptic cloud provider error messages into actionable guidance. Enable with --copilot flag and let us know what you think!"
 ---
 
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 We're excited to announce the new AI capabilities for Pulumi CLI powered by Pulumi Copilot that translate complex infrastructure changes into clear, human-readable explanations and help resolve deployment errors with actionable guidance. Enable these preview features with the `--copilot` flag.
 
 <!--more-->

content/blog/codegen-learnings/index.md

@@ -15,6 +15,10 @@ tags:
 
 ---
 
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 When asked about his research process, Anthony Bourdain would describe how he'd blend his formal culinary training with deep dives into local food culture - from market stalls to family recipes. Modern AI code generation follows a similar path: it can't just rely on what it knows - it must tap into continuously evolving, domain-specific knowledge bases. Just as Bourdain would combine his classical French training with techniques learned from local kitchens, AI code generators blend their built-in knowledge with retrieved code snippets and type definitions to generate code that accurately represents the user's intent.
 
 This fusion of base knowledge with contextual understanding is especially valuable for Infrastructure as Code (IaC), where rapidly evolving cloud providers and libraries make manual development challenging, traditional debugging cycles impractical, and errors catastrophically expensive.
@@ -232,9 +236,9 @@ As we continue to evolve Pulumi's code generation capabilities, we're excited ab
 
 We invite you to try these capabilities in your own projects and share your experiences. Your feedback helps us continue improving and advancing the state of AI-assisted infrastructure development.
 
-<!--raw material 
+<!--raw material
 
-1.2. get multiple "Pulumi Registry schema" elements (40 in our case, 29 unique) - some of them less relevant. 
+1.2. get multiple "Pulumi Registry schema" elements (40 in our case, 29 unique) - some of them less relevant.
 (We call them tokens internally but they are really type names)
 This search uses vector embeddings
 
@@ -283,15 +287,15 @@ Resulting generated prompt can be 1K or more lines of Yaml
 
 4. Full text search and BM25
 
-BM25: 
+BM25:
 - Inverse Document Frequency: how rare is the query term
 - Term frequency in the document: how often does the term appear in the document
 Detailed explanation: https://emschwartz.me/understanding-the-bm25-full-text-search-algorithm/
 
 5. Vector embeddings, combine the two
 similarity metrics like cosine similarity.
 
-6. Reranking 
+6. Reranking
 
 6.1. It's good to have good recall - you can throw everything and the kitchen sink at the LLM - but too much information can actually be counterproductive:
 
@@ -318,6 +322,6 @@ How do we assess the quality of our RAG? Intuitively, we want two things to be t
 
 - Recall
 - Typecheck
-- `pulumi up` - a "dry run" before the actual deployment and can detect many real or potential problems such potentially destructive actions, incorrect configurations that cannot be detected at compile time, dependency conflicts and policy violations. 
+- `pulumi up` - a "dry run" before the actual deployment and can detect many real or potential problems such potentially destructive actions, incorrect configurations that cannot be detected at compile time, dependency conflicts and policy violations.
 
 -->

content/blog/copilot-in-docs/index.md

@@ -16,6 +16,10 @@ social:
     twitter: "Pulumi Copilot is now available across Pulumi Documentation and pulumi.com, and comes equipped with a powerful new Documentation Skill! Learn more by reading our blog:"
 ---
 
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 [Pulumi Copilot](/docs/pulumi-cloud/copilot/) has been making our customers' day-to-day tasks easier since its release, and today we’re excited to expand its capabilities—Pulumi Copilot is now available across Pulumi Documentation and pulumi.com, and comes equipped with a powerful new Documentation Skill!
 
 <!--more-->

content/blog/copilot-in-vscode/index.md

@@ -42,11 +42,16 @@ tags:
 
 social:
     twitter: "🎉 Pulumi Copilot is now available in Visual Studio Code! Offload tasks to Pulumi Copilot right in your IDE by typing @pulumi in Copilot Chat. Build, deploy, and manage cloud infrastructure more efficiently than ever."
-    linkedin: "Exciting news! Pulumi Copilot is now available in Visual Studio Code Copilot, bringing AI-powered cloud infrastructure management directly to your IDE. Simply install the Pulumi extension and type @pulumi in Copilot Chat to access Pulumi's cloud intelligence and streamline your infrastructure workflows. 
-    
+    linkedin: "Exciting news! Pulumi Copilot is now available in Visual Studio Code Copilot, bringing AI-powered cloud infrastructure management directly to your IDE. Simply install the Pulumi extension and type @pulumi in Copilot Chat to access Pulumi's cloud intelligence and streamline your infrastructure workflows.
+
     Learn how Pulumi Copilot is revolutionizing cloud development: [Link]"
 
 ---
+
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 Programming languages offer dozens of advantages for writing Infrastructure as Code (IaC). One of them is that Large Language Models are  effective at using general-purpose programming languages, thanks to the vast amount of high-quality training data available. Building on this advantage, we introduced Pulumi AI and Pulumi Copilot last year to enhance Infrastructure-as-Code development with generative AI capabilities. These tools have significantly streamlined infrastructure deployment for tens of thousands of developers.
 
 Today, we are thrilled to announce that Pulumi Copilot is now available directly within [Pulumi Copilot Chat Extension](https://marketplace.visualstudio.com/items?itemName=pulumi.pulumi-vscode-copilot). By simply typing @pulumi in Copilot Chat, developers can now access the power of Pulumi Copilot right within their IDE, saving them time on writing IaC and getting infrastructure deployed.

content/blog/copilot-lessons/index.md

@@ -13,13 +13,18 @@ tags:
     - ai
     - iac
 social:
-    twitter: > 
+    twitter: >
         Building Pulumi Copilot taught us key lessons about AI-powered tools: hallucinations reveal missing features, prompt engineering isn’t always the answer, and balancing LLMs with traditional code is critical. Learn more: https://www.pulumi.com/blog/copilot-lessons/
     linkedin: |
         Building AI-powered tools often brings unexpected challenges—and valuable lessons. While developing Pulumi Copilot, we encountered surprising insights: hallucinations revealed missing product features, prompt engineering wasn't always the fix, and balancing LLM capabilities with traditional code proved essential.
         One memorable turning point came from user feedback: "Your tool doesn't know anything!" Instead of seeing it as failure, we saw opportunity—leading to significant improvements.
         Curious how we turned unexpected challenges into product breakthroughs? Learn more: https://www.pulumi.com/blog/copilot-lessons/
 ---
+
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 Building AI-powered developer tools comes with unique challenges, and now that we've **[launched our REST API](/blog/pulumi-copilot-rest/)**, we want to share some lessons we've learned building Pulumi Copilot, an AI assistant for cloud infrastructure.
 
 One of the big challenges was determining what 'working' really meant. So when a message landed in our feedback channel after months of rigorous testing - 'Your tool doesn't know anything!' - it caused some mild panic. We'd just made some changes, so we braced for the worst. But our evals were still looking strong, so what was going on?
@@ -62,7 +67,7 @@ These early experiences showed the value of Copilot. But they also revealed the
 
 ## Skillful Slicing: Modular Mastery
 
-As Copilot grew, we broke it into smaller pieces we call skills. Each skill does one specific job. The Insights skill handles queries about resource usage and configuration ("How many S3 buckets do I have?"), the Cloud Skill interacts with the Pulumi Service API to manage infrastructure ("Show me my stacks."), the Code Skill generates Pulumi code snippets ("Write a Typescript program..."), and the Docs Skill retrieves information from Pulumi documentation ("How do I use [update plans](https://www.pulumi.com/docs/iac/concepts/update-plans/)?").  
+As Copilot grew, we broke it into smaller pieces we call skills. Each skill does one specific job. The Insights skill handles queries about resource usage and configuration ("How many S3 buckets do I have?"), the Cloud Skill interacts with the Pulumi Service API to manage infrastructure ("Show me my stacks."), the Code Skill generates Pulumi code snippets ("Write a Typescript program..."), and the Docs Skill retrieves information from Pulumi documentation ("How do I use [update plans](https://www.pulumi.com/docs/iac/concepts/update-plans/)?").
 
 When you ask Copilot something, it figures out what you need and picks the right skill for the job – like a manager deciding which expert to send your question to. This [function-calling](https://platform.openai.com/docs/guides/function-calling) approach, orchestrated by a component we call the "outer loop," allows Copilot to access and process information beyond its internal knowledge base.
 

content/blog/copilot-system-prompts/index.md

@@ -13,6 +13,10 @@ tags:
     - releases
 ---
 
+{{< notes type="info" >}}
+Note: This post discusses Pulumi Copilot, which Pulumi Neo has replaced. [Learn about Neo →](/docs/ai/)
+{{< /notes >}}
+
 We are excited to announce a new feature for Pulumi Copilot: System Prompts. This enhancement empowers organizations to customize Pulumi Copilot's responses for your organization, making your interactions with our AI assistant even more personalized to save you even more time.
 
 <!--more-->

content/blog/day-2-operations-drift-detection-and-remediation/index.md

@@ -1,5 +1,5 @@
 ---
-title: "Day 2 Operations: Drift Detection and Remediation | IDP Workshop"
+title: "Day 2 Operations: Drift Detection and Remediation"
 allow_long_title: true
 meta_desc: "Implement automated drift detection for your IDP using Pulumi. Maintain infrastructure integrity with scheduled checks and real-time alerts."
 meta_image: meta.png
@@ -22,7 +22,7 @@ tags:
 
 social:
     twitter: |
-        Day 2 Operations: Drift Detection and Remediation | IDP Workshop
+        Day 2 Operations: Drift Detection and Remediation
 
         Learn how to maintain infrastructure integrity with automated drift detection:
         • Understand drift in cloud infrastructure
@@ -34,7 +34,7 @@ social:
 
         #IDP #DriftDetection #PlatformEngineering #InfrastructureAsCode #DevOps
     linkedin: |
-        **Day 2 Operations: Drift Detection and Remediation | IDP Workshop**
+        **Day 2 Operations: Drift Detection and Remediation**
 
         In the fourth post of our IDP Best Practices series, we explore the critical day 2 operations that ensure your infrastructure stays aligned with your intended configuration long after initial deployment.
 

content/blog/deployment-guardrails-with-policy-as-code/index.md

@@ -31,7 +31,7 @@ This post is part of our IDP Best Practices series:
 * [How to Build an Internal Developer Platform: Strategy, Best Practices, and Self-Service Infrastructure](/blog/idp-strategy-planning-self-service-infrastructure-that-balances-developer-autonomy-with-operational-control)
 * [Build Golden Paths with Infrastructure Components and Templates](/blog/golden-paths-infrastructure-components-and-templates)
 * **Deployment Guardrails with Policy as Code** (you are here)
-* Day 2 Platform Operations: Automating Drift Detection and Remediation
+* [Day 2 Operations: Drift Detection and Remediation](/blog/day-2-operations-drift-detection-and-remediation)
 * Extend Your IDP for AI Applications: GPUs, Models, and Cost Controls
 * Next-Gen IDPs: How to Modernize Legacy Infrastructure with Pulumi