Merge branch 'master' into copilot-neo-redirect-audit

Author: asafashirov

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
 

content/blog/golden-paths-infrastructure-components-and-templates/index.md

@@ -36,7 +36,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: Guide to Reusable Infrastructure with Pulumi Components and Templates** (you are here)
 - [Policy as Code for Safer IDPs: Enabling Developer Self-Service with Guardrails](/blog/deployment-guardrails-with-policy-as-code)
-- 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
 

content/blog/idp-strategy-planning-self-service-infrastructure-that-balances-developer-autonomy-with-operational-control/index.md

@@ -82,7 +82,7 @@ This post is part of our IDP Best Practices series. You can explore the full ser
 - **How to Build an Internal Developer Platform: Strategy, Best Practices, and Self-Service Infrastructure** (you are here)
 - [Build Golden Paths: Guide to Reusable Infrastructure with Pulumi Components and Templates](/blog/golden-paths-infrastructure-components-and-templates/)
 - [Policy as Code for Safer IDPs: Enabling Developer Self-Service with Guardrails](/blog/deployment-guardrails-with-policy-as-code)
-- 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
 

content/docs/iac/guides/building-extending/components/build-a-component.md

@@ -41,6 +41,10 @@ Pulumi Components are implemented as custom classes in any Pulumi-supported lang
 
 Pulumi Components inherently support multi-language use. Regardless of the language a component was written in, it is a fast one-step process to generate a SDK, allowing you to use it in all Pulumi-supported languages.
 
+{{< notes type="warning" >}}
+If your component uses a local package (such as any Terraform provider via `terraform-provider`, or another component that contains a local package), you must commit the generated SDK code to version control. See [Using components with local packages](/docs/iac/guides/building-extending/packages/local-packages/#components-with-local-packages) for details.
+{{< /notes >}}
+
 ## Structure of a Component
 
 A Pulumi Component consists of three main parts:

content/docs/iac/guides/building-extending/packages/local-packages.md

@@ -66,10 +66,10 @@ This clones the repo and executes the source, enabling you to use packages from
 #### Using `terraform-provider`
 
 ```bash
-pulumi package add terraform-provider hashicorp/random
+pulumi package add terraform-provider hashicorp/random 3.5.1
 ```
 
-Refer to the [Terraform Provider documentation](/docs/iac/using-pulumi/pulumi-packages/terraform-provider/) for more details.
+Refer to the [Any Terraform Provider documentation](/docs/iac/using-pulumi/pulumi-packages/terraform-provider/) for more details.
 
 ## Using generated SDKs
 
@@ -206,11 +206,42 @@ When working with local packages, it's important to understand how breaking chan
   To ensure stability, you should specify the version of both:
 
   ```bash
-  pulumi package add terraform-provider hashicorp/random --version=3.5.1
+  pulumi package add terraform-provider hashicorp/random 3.5.1
   ```
 
   This pins the Terraform provider version, protecting you from unexpected breaking changes when the underlying provider is updated.
 
+## Using components with local packages {#components-with-local-packages}
+
+When creating a component that contains a local package, you must ensure the generated SDK is available to consumers of your component. This applies when your component uses:
+
+- Any Terraform provider via [`terraform-provider`](/registry/packages/terraform-provider/)
+- Another component that itself contains a local package
+- Any other Pulumi plugin that generates code in the `sdk` folder
+
+### Requirements
+
+1. You must be using Pulumi 3.200.0 or later.
+1. In your component code, run `pulumi package add` to generate the upstream SDK.
+1. Ensure the generated code in the `sdk` folder is committed to version control.
+
+### Why this is necessary
+
+When someone consumes your component, they need access to all the SDKs your component depends on. For published packages from the Pulumi Registry, these dependencies are automatically resolved. However, for local packages generated within your component, the generated SDK code must be available in your repository so that consumers can use it.
+
+### Example workflow
+
+If you're building a component that uses a Terraform provider:
+
+```bash
+cd my-component
+pulumi package add terraform-provider hashicorp/random 3.5.1
+git add sdk/
+git commit -m "Add generated SDK for terraform-provider random"
+```
+
+Consumers of your component will then be able to use it without needing to regenerate the SDK themselves.
+
 ## See also
 
 For more information about developing and publishing your own packages, see the [Publishing Packages](/docs/iac/build-with-pulumi/publishing-packages/) guide.

content/docs/iac/guides/building-extending/packages/publishing-packages.md

@@ -21,14 +21,26 @@ aliases:
 - /docs/iac/build-with-pulumi/publishing-packages/
 ---
 
-This guide will take you step-by-step through creating and publishing a Pulumi Package. You can use this guide to create any [type of Pulumi Package](/docs/guides/pulumi-packages#types-of-pulumi-packages): a component, custom provider, or an existing Terraform provider packaged for use within Pulumi. This guide assumes you're using GitHub to host your package's source code and GitHub Actions to publish various parts of your package.
+This guide will take you through the process to create and publish a [Pulumi Package](/docs/iac/concepts/packages) to the [Pulumi Registry](/registry). You can use this guide to publish the following types of Pulumi Packages:
+
+- A [component](/docs/iac/concepts/components) or related group of components
+- A custom provider where you define the CRUD operations for each resource type
+- A bridged provider, which wraps an existing Terraform provider and leverages its code to perform the CRUD operations for each resource type
+
+{{% notes type="info" %}}
+This guide is for creating packages for public consumption. If you are a looking for information on how to create and publish components for use within your organization, see [Build a Component](/docs/iac/guides/building-extending/components/build-a-component).
+{{% /notes %}}
 
 {{% notes type="info" %}}
-If you are a cloud or SaaS provider interested in publishing a Pulumi provider or component, please [reach out partners team](/contact/?form=registry) to start publishing to the Pulumi Registry.
+If you are a cloud or SaaS provider interested in publishing a Pulumi provider or component, please [reach out to our partners team](/contact).
 {{% /notes %}}
 
 ## Prerequisites
 
+{{% notes type="info" %}}
+This guide assumes you're using GitHub to host your package's source code and GitHub Actions to publish various parts of your package.
+{{% /notes %}}
+
 - You need to [install Pulumi](/docs/install/).
 - You should be familiar with the Pulumi [Resource and Component model](/docs/concepts/resources/).
 - Pulumi Packages are multi-language: you can write your package once in either Go, Python, or TypeScript/JavaScript and then make it available to all Pulumi users, even if they use another language. To develop them, you need to have Git, Go, .NET, Python, and TypeScript installed on your system.
@@ -46,7 +58,7 @@ We've created some template repositories for you to use as a starting point for
 - Bridge an existing Terraform Provider to use with Pulumi: [`pulumi/pulumi-tf-provider-boilerplate`](https://github.com/pulumi/pulumi-tf-provider-boilerplate)
 
 {{% notes type="info" %}}
-If you need access to a Terraform provider, but don't need the full customisation of a published provider, the ["Any Terraform Provider" Pulumi Provider](/registry/packages/terraform-provider) can provide instant access via locally generating SDKs.
+If you need access to a Terraform provider, but don't need the full customization of a published provider, the ["Any Terraform Provider" Pulumi Provider](/registry/packages/terraform-provider) can provide instant access via locally generating SDKs.
 {{% /notes %}}
 
 ### Name your provider and repository

content/events/getting-started-with-infrastructure-agents/get-started-ai-agent.png

@@ -2,7 +2,7 @@
 # Name of the event, <= 60 characters
 title: "Getting Started with Infrastructure Agents"
 meta_desc: Learn to add intelligent automation to infrastructure workflows with proper controls and human oversight.
-meta_image:
+meta_image: /images/resources/get-started-ai-agent.png
 
 # A featured webinar will display first in the list.
 featured: false
@@ -12,7 +12,7 @@ unlisted: false
 
 # Gated webinars will have a registration form and the user will need
 # to fill out the form before viewing.
-gated: true
+gated: false
 
 # The layout of the landing page.
 type: webinars
@@ -35,13 +35,13 @@ main:
     event_type: workshop # workshop | event
 
     # URL for embedding a URL for ungated webinars.
-    youtube_url:
+    youtube_url: https://www.youtube.com/embed/_6abaK-dCz0?si=3assXiKb1H-jKMF7
 
     # Sortable date. The datetime Hugo will use to sort the webinars in date order.
     sortable_date: 2025-10-14T12:00:00-04:00
 
     # Duration of the webinar.
-    duration: 90 minutes
+    duration: 60 minutes
 
     # "virtual" will be shown under "show virtual events only", otherwise shown as City, State (seattle, wa)
     location: virtual
@@ -64,7 +64,7 @@ main:
     # case-sensitive
     tags:
         level: Beginner # Beginner, Intermediate, Advanced
-        topics:  ["Pulumi MCP Server"]
+        topics:  ["AI", "Infrastructure as Code", "Platform Engineering", "Pulumi Neo"]
         languages: ["Any"]
         clouds: ["AWS"]