Add HCL templates to template pages by cnunciato · Pull Request #19831 · pulumi/docs

cnunciato · 2026-06-24T01:01:28Z

Adds HCL as a selectable language across the architecture template pages, paired with the new HCL templates in pulumi/templates#1141.

Adds hcl as an option to the language chooser and partials
Adds - hcl to each page's template.languages and to the meta_desc/index copy.
Makes the config/outputsections HCL-aware: HCL templates use snake_case names with some different defaults, extra/dropped variables, and different outputs, so each diverging definition list, example command, and intro is wrapped in language choosables — non-HCL readers are unchanged.
Adds an HCL walkthrough for the static-website/aws "Adding a custom domain" example and a cache-settings snippet.
Corrects the kubernetes/aws eksNodeInstanceType default (t2.medium → t3.medium) to match the actual templates.

⚠️ Do not merge before pulumi/templates#1141 merges. The HCL templates these pages reference (<prefix>-hcl) won't exist in pulumi/templates until that PR lands.

Closes https://github.com/pulumi/marketing/issues/1771.

Register HCL in the language chooser and add it across the architecture template pages, with HCL-aware config/output documentation (snake_case names, defaults, and per-template differences) derived from the new HCL templates in pulumi/templates#1141. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

pulumi-bot · 2026-06-24T01:07:56Z

Your site preview for commit 7354047 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-19831-73540478.s3-website.us-west-2.amazonaws.com

pulumi-bot · 2026-06-24T01:10:32Z

Lighthouse Performance Report

Commit: 7354047 | Metric definitions

Page	Device	Score	FCP	LCP	TBT	CLS	SI
Homepage	Mobile	🟡 55	3.0s	5.3s	780ms	0.076	3.0s
Homepage	Desktop	🟡 78	0.7s	2.4s	236ms	0.016	1.1s
Install Pulumi	Mobile	🟡 61	5.3s	8.6s	52ms	0.057	5.3s
Install Pulumi	Desktop	🟢 90	1.1s	1.7s	0ms	0.012	1.1s
AWS Get Started	Mobile	🟡 60	5.1s	8.5s	56ms	0.092	5.1s
AWS Get Started	Desktop	🟡 78	1.1s	2.5s	0ms	0.024	2.6s

The HCL templates were reworked to use native Pulumi providers, which changed several config/output surfaces. Reconcile the affected pages: - container/aws: drop app_path/image_name, cpu/memory defaults now 512/128 - container/azure: drop location, add image_tag - kubernetes/aws: drop cluster_name output - kubernetes/azure, vm/azure: drop location - serverless/aws: no config settings; single url output - serverless/azure: site_url -> origin_url; drop location - static-website/azure: drop CDN outputs (template now origin-only); drop location Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

github-actions · 2026-06-26T00:54:24Z

Pre-merge Review — Last updated 2026-06-26T00:43:20Z

Tip

Summary: This PR adds HCL (Terraform-language) variants to all 18 Pulumi template guide pages under content/templates/ — container-service, kubernetes, kubernetes-application, serverless-application, static-website, and virtual-machine across AWS/Azure/Google Cloud — by wrapping the existing per-language content in choosable blocks, adding parallel HCL configuration/output/walkthrough blocks, and wiring hcl into the chooser machinery (chooser.tsx, the langfile shortcodes, and the languages partial). The failure mode that would block a reader is an HCL config key, default value, stack-output name, or walkthrough step that doesn't match the actual HCL templates. Mechanics, frontmatter, and the chooser/langfile wiring are internally consistent; claim verification across 263 extracted claims found the new HCL content self-consistent, and the contradictions all trace to pre-existing non-HCL text or to verification artifacts (claims checked against a paraphrase or against external sources rather than the page's own walkthrough code) rather than to new errors. The remaining low-confidence items are an HCL-only service_port setting and a pre-existing "all DNS providers" overclaim, both flagged for author confirmation.

Review confidence:

Dimension	Level	Notes
mechanics	HIGH
facts	MEDIUM	new HCL content is self-consistent; the 6 contradictions are pre-existing non-HCL text or verification artifacts, and a few new HCL template config/output claims couldn't be independently verified (author to confirm)
code correctness	HIGH	HCL snippets and the `chooser.tsx`/`langfile` wiring parse and are consistent

Investigation log

Cross-sibling reads: not run (not in a templated section)
External claim verification: 243 of 263 claims verified (9 unverifiable, 6 contradicted) · 4 specialists (numerical, cross-reference, capability, framing); 0 cross-specialist corroborations · routed: 0 inline, 254 Pass 1, 0 Pass 2, 9 Pass 3 (verified 6, contradicted 0, unverifiable 3).
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: ran (3 specialists: structural, existence, body-code-coverage); 0 findings
Editorial-balance pass: not run (not under content/blog/)

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

🔍 Verification trail

263 claims extracted · 243 verified · 9 unverifiable · 6 contradicted

L4 in content/templates/_index.md "Pulumi templates are available in HCL (in addition to TypeScript, Python, Go, .NET/C#, and YAML)." → ✅ verified (evidence: The file content/templates/_index.md explicitly states in its description: "Pulumi templates are starter projects for common cloud architectures on AWS, Azure, and Google Cloud, available in TypeScript, Python, Go, .NET/C#, YAML, and HCL…; source: repo:content/templates/_index.md)
L6 in content/templates/container-service/aws/index.md "The Container Service on AWS template supports HCL as a language option, in addition to TypeScript, Python, Go, C#, and YAML." → ✅ verified (evidence: The file at content/templates/container-service/aws/index.md explicitly lists hcl in the languages array alongside typescript, python, go, csharp, and yaml, and the meta_desc reads "Deploy a container service on AWS with…; source: repo:content/templates/container-service/aws/index.md)
L62 in content/templates/container-service/aws/index.md "For non-HCL languages (TypeScript, Python, Go, C#, YAML), the Container Service template has a container_port configuration setting that specifies the port m…" → ✅ verified (evidence: The file at L62 area contains, under {{% choosable language "typescript,python,go,csharp,yaml" %}}: "container_port: Specifies the port mapping for the container. Defaults to port 80." — exactly matching the claim for non-HCL languages.; source: repo:content/templates/container-service/aws/index.md)
L70-71 in content/templates/container-service/aws/index.md "For non-HCL languages (TypeScript, Python, Go, C#, YAML), the Container Service template has an image configuration setting that specifies the location of th…" → ✅ verified (evidence: The file at lines ~70-71 (within the {{% choosable language "typescript,python,go,csharp,yaml" %}} block) states: "image: Specifies the location of the Dockerfile used to build the container image that is run. Defaults to the Dockerfile…; source: repo:content/templates/container-service/aws/index.md)
L78 in content/templates/container-service/aws/index.md "The HCL variant of the Container Service template has an app_path configuration setting that specifies the path to the container application to deploy, used…" → ✅ verified (evidence: The file content/templates/container-service/aws/index.md contains exactly: "app_path: Specifies the path to the container application to deploy, used as the build context for the Dockerfile. Defaults to ./app." inside the `{{% choosab…; source: repo:content/templates/container-service/aws/index.md)
L81 in content/templates/container-service/aws/index.md "The HCL variant of the Container Service template has an image_name configuration setting that specifies the name to give the container image that is built,…" → ✅ verified (evidence: The file content/templates/container-service/aws/index.md contains, within the {{% choosable language hcl %}} block: "image_name\n: Specifies the name to give the container image that is built. Defaults to my-app." — exactly matching…; source: repo:content/templates/container-service/aws/index.md)
L84 in content/templates/container-service/aws/index.md "The HCL variant of the Container Service template has a container_port configuration setting that specifies the port mapping for the container, and defaults…" → ✅ verified (evidence: The HCL-specific choosable block in the file reads: "container_port: Specifies the port mapping for the container. Defaults to 80." — exactly matching the claim.; source: repo:content/templates/container-service/aws/index.md)
L87 in content/templates/container-service/aws/index.md "The HCL variant of the Container Service template has a cpu configuration setting that specifies the amount of CPU to use with each task or each container wi…" → ✅ verified (evidence: The file at content/templates/container-service/aws/index.md contains, within the {{% choosable language hcl %}} block: "cpu: Specifies the amount of CPU to use with each task or each container within a task. Defaults to 256." — exac…; source: repo:content/templates/container-service/aws/index.md)
L90 in content/templates/container-service/aws/index.md "The HCL variant of the Container Service template has a memory configuration setting that specifies the amount of memory to use with each task or each contai…" → ✅ verified (evidence: The file at content/templates/container-service/aws/index.md contains, within the {{% choosable language hcl %}} block: "memory: Specifies the amount of memory to use with each task or each container within a task. Defaults to 512."…; source: repo:content/templates/container-service/aws/index.md)
L94 in content/templates/container-service/aws/index.md "All configuration settings for the Container Service template are optional and may be adjusted by editing the stack configuration file directly (by default, P…" → ✅ verified (evidence: The file at L94 reads: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set`]" — an exact match…; source: repo:content/templates/container-service/aws/index.md)
L100 in content/templates/container-service/aws/index.md "For the TypeScript, Python, Go, C#, and YAML Container Service templates, a custom container image can be configured using the image setting to point to anot…" → ✅ verified (evidence: The file explicitly states under the TypeScript/Python/Go/C#/YAML choosable block: "configuring the stack to point to another folder on your computer with the image setting" and lists image as a config setting that "Specifies the locat…; source: repo:content/templates/container-service/aws/index.md)
L111 in content/templates/container-service/aws/index.md "For the HCL variant of the Container Service template, a custom container image can be configured by setting the app_path configuration setting to point to a…" → ✅ verified (evidence: The file at content/templates/container-service/aws/index.md contains an HCL-specific section that reads: "you can do so either by replacing the Dockerfile in the app folder or by configuring the stack to point to another folder on you…; source: repo:content/templates/container-service/aws/index.md)
L114 in content/templates/container-service/aws/index.md "The pulumi config set app_path ../my-existing-image command configures the HCL Container Service template to use a custom container image path." → ✅ verified (framing: strengthened — the source says app_path sets "the path to the container application to deploy, used as the build context for the Dockerfile"; the claim narrows…; evidence: The file explicitly shows the HCL-specific block: "configuring the stack to point to another folder on your computer (one containing a Dockerfile) with the app_path setting" followed by the code snippet `$ pulumi config set app_path ../m…; source: repo:content/templates/container-service/aws/index.md)
L6 in content/templates/container-service/azure/index.md "The Container Service on Azure template supports HCL as a language option, in addition to TypeScript, Python, Go, and C#." (also L17) → ✅ verified (evidence: The file at lines 6 and 12–17 explicitly lists HCL alongside TypeScript, Python, Go, and C#: meta_desc: "...in TypeScript, Python, Go, C#, or HCL." and the languages: array includes typescript, python, go, csharp, and hcl.; source: repo:content/templates/container-service/azure/index.md)
L17 in content/templates/container-service/azure/index.md "The Container Service on Azure template includes HCL as a supported language." → ✅ verified (evidence: The file's front matter lists hcl under template.languages alongside typescript, python, go, and csharp, and the meta_desc reads "…in TypeScript, Python, Go, C#, or HCL."; source: repo:content/templates/container-service/azure/index.md)
L64 in content/templates/container-service/azure/index.md "For the TypeScript, Python, Go, and C# variants of the Container Service on Azure template, the configuration settings include appPath, containerPort, and…" (also L110) → ❌ contradicted (framing: shifted — claim says non-HCL variants do NOT include cpu and memory (listing them as HCL-specific), but the source shows both settings appear in the TypeSc…; evidence: The file shows that cpu and memory appear in BOTH the TypeScript/Python/Go/C# block AND the HCL block, so they are not HCL-specific. The claim incorrectly implies cpu and memory are HCL-specific settings absent from the non-HCL var…; source: repo:content/templates/container-service/azure/index.md)
L89 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has a location configuration setting that defaults to WestUS." → ✅ verified (evidence: The file content/templates/container-service/azure/index.md in the HCL choosable block explicitly states: "location: The Azure region to deploy into. Defaults to WestUS." — exactly matching the claim.; source: repo:content/templates/container-service/azure/index.md)
L92 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has an app_path configuration setting that defaults to ./app, which contains a 'Hello world' exa…" → ✅ verified (evidence: The file at content/templates/container-service/azure/index.md in the HCL choosable block states: "app_path: The path to the folder containing the application and Dockerfile. Defaults to ./app, which contains a 'Hello world' example."…; source: repo:content/templates/container-service/azure/index.md)
L95 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has an image_name configuration setting that defaults to my-app." → ✅ verified (evidence: The file content/templates/container-service/azure/index.md under the {{% choosable language hcl %}} section explicitly states: "image_name: The name of the container image to be published to Azure Container Registry. Defaults to `my-a…; source: repo:content/templates/container-service/azure/index.md)
L98 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has a container_port configuration setting that defaults to 80." → ✅ verified (evidence: The file at content/templates/container-service/azure/index.md contains an HCL-specific choosable block that reads: "container_port: The port to expose on the container. Defaults to 80." This directly confirms the claim.; source: repo:content/templates/container-service/azure/index.md)
L101 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has a cpu configuration setting that defaults to 1 CPU core." → ✅ verified (evidence: The HCL choosable block in content/templates/container-service/azure/index.md explicitly states: "cpu: The number of CPU cores to allocate on the container. Defaults to 1."; source: repo:content/templates/container-service/azure/index.md)
L104 in content/templates/container-service/azure/index.md "The HCL variant of the Container Service on Azure template has a memory configuration setting (in GB) that defaults to 2." → ✅ verified (evidence: The file at content/templates/container-service/azure/index.md explicitly lists under the HCL choosable block: "memory: The amount of memory, in GB, to allocate on the container. Defaults to 2."; source: repo:content/templates/container-service/azure/index.md)
L108 in content/templates/container-service/azure/index.md "All configuration settings for the Container Service on Azure template are optional and may be adjusted by editing the stack configuration file directly (by de…" → ✅ verified (evidence: The file at L108 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set]", which matches…; source: repo:content/templates/container-service/azure/index.md)
L113 in content/templates/container-service/azure/index.md "In the HCL variant of the Container Service on Azure template, the container port configuration setting is named container_port (set via pulumi config set c…" (also L122) → ✅ verified (evidence: The file at content/templates/container-service/azure/index.mdexplicitly listscontainer_portas the HCL config setting ("The port to expose on the container. Defaults to80.") and shows the exact command $ pulumi config set contai…; source: repo:content/templates/container-service/azure/index.md)
L113 in content/templates/container-service/azure/index.md "In the TypeScript/Python/Go/C# variants of the Container Service on Azure template, the container port configuration setting is named containerPort (set via…" → ✅ verified (evidence: The file explicitly lists containerPort as a config setting for the {{% choosable language "typescript,python,go,csharp" %}} block, and the example command shown is $ pulumi config set containerPort 8080.; source: repo:content/templates/container-service/azure/index.md)
L6 in content/templates/container-service/gcp/index.md "The Container Service on Google Cloud template supports HCL as a language option (in addition to TypeScript, Python, Go, and C#)." → ✅ verified (evidence: The file at content/templates/container-service/gcp/index.md lists languages: [typescript, python, go, csharp, hcl] and the meta_desc reads "Deploy a container service on Google Cloud with Pulumi, Cloud Run, and Artifact Registry in…; source: repo:content/templates/container-service/gcp/index.md)
L17 in content/templates/container-service/gcp/index.md "The Container Service on Google Cloud template includes an HCL language variant." → ✅ verified (evidence: The file's frontmatter explicitly lists hcl under template.languages (alongside typescript, python, go, csharp), and the page body contains multiple HCL-specific {{% choosable language hcl %}} sections confirming the HCL variant is i…; source: repo:content/templates/container-service/gcp/index.md)
L45 in content/templates/container-service/gcp/index.md "The HCL template for Container Service on Google Cloud deploys into the active Google Cloud project read from gcloud credentials." → ✅ verified (evidence: The file at content/templates/container-service/gcp/index.md contains the exact statement in the HCL choosable block: "The template deploys into your active Google Cloud project (read from your gcloud credentials) and defaults to the `us-c…; source: repo:content/templates/container-service/gcp/index.md)
L71 in content/templates/container-service/gcp/index.md "The containerPort configuration setting for the Container Service template (TypeScript/Python/Go/C#) defaults to port 8080." → ✅ verified (evidence: The index.md file at L71 states "The port mapping for the container service. Defaults to port 8080." and all four language templates in pulumi/templates confirm this: TypeScript uses || 8080, Python uses `get_int("containerPort", 8080)…; source: repo:content/templates/container-service/gcp/index.md and gh search code pulumi/templates containerPort 8080)
L93 in content/templates/container-service/gcp/index.md "The HCL region configuration setting for the Container Service on Google Cloud template defaults to us-central1." → ✅ verified (evidence: The file explicitly states under the HCL-specific configuration section: "region: The Google Cloud region to deploy into. Defaults to us-central1." It also states earlier: "defaults to the us-central1 region, which you can change with…; source: repo:content/templates/container-service/gcp/index.md)
L96 in content/templates/container-service/gcp/index.md "The HCL Container Service template's app_path configuration setting defaults to the app folder, which contains a 'Hello World' example app." → ✅ verified (evidence: The file at content/templates/container-service/gcp/index.md in the HCL choosable block states: "app_path: The location of the Dockerfile used to build the container image. Defaults to the app folder, which contains a 'Hello World' exa…; source: repo:content/templates/container-service/gcp/index.md)
L99 in content/templates/container-service/gcp/index.md "The HCL Container Service template exposes an image_name configuration setting for the name of the container image deployed to Cloud Run, defaulting to my-a…" → ✅ verified (evidence: The file's HCL choosable block explicitly states: "image_name : The name of the container image deployed to your Cloud Run service. Defaults to my-app`." — exactly matching the claim.; source: repo:content/templates/container-service/gcp/index.md)
L102 in content/templates/container-service/gcp/index.md "The HCL container_port configuration setting for the Container Service template defaults to port 8080." → ✅ verified (evidence: The file explicitly states under the HCL choosable block: "container_port: The port mapping for the container service. Defaults to port 8080."; source: content/templates/container-service/gcp/index.md)
L105 in content/templates/container-service/gcp/index.md "The HCL Container Service template's cpu configuration setting defaults to 1 CPU per container instance." → ✅ verified (evidence: The file content/templates/container-service/gcp/index.md contains, within the {{% choosable language hcl %}} block: "cpu\n: The amount of CPU to allocate to each container instance. Defaults to 1 CPU." — exactly matching the claim.; source: repo:content/templates/container-service/gcp/index.md)
L108 in content/templates/container-service/gcp/index.md "The HCL Container Service template's memory configuration setting defaults to 1Gi per container instance." → ✅ verified (evidence: The file content/templates/container-service/gcp/index.md contains, in the HCL-specific choosable block: "memory\n: The amount of memory to allocate to each container instance. Defaults to 1Gi." — directly confirming the claim.; source: repo:content/templates/container-service/gcp/index.md)
L111 in content/templates/container-service/gcp/index.md "The HCL concurrency configuration setting specifies the maximum number of concurrent requests per container instance and defaults to 80." → ✅ verified (evidence: The file's HCL-specific {{% choosable language hcl %}} section explicitly states: "concurrency: The maximum number of concurrent requests per container instance. Defaults to 80." This matches the claim exactly (note: the non-HCL langua…; source: repo:content/templates/container-service/gcp/index.md)
L115 in content/templates/container-service/gcp/index.md "All configuration settings for the Container Service template are optional and may be adjusted by editing the stack configuration file directly (by default, P…" → ✅ verified (framing: strengthened — claim says "using pulumi config set" while source says "changing their values with pulumi config set"; the claim is a narrower paraphrase th…; evidence: The file at content/templates/container-service/gcp/index.md states verbatim: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml`) or by changing th…; source: repo:content/templates/container-service/gcp/index.md)
L129 in content/templates/container-service/gcp/index.md "For the HCL variant, the container port configuration setting is named container_port (set via pulumi config set container_port 3000)." → ✅ verified (evidence: The file at content/templates/container-service/gcp/index.md explicitly lists container_port under the HCL choosable block and shows the exact command $ pulumi config set container_port 3000 in the HCL code snippet.; source: repo:content/templates/container-service/gcp/index.md)
L6 in content/templates/kubernetes-application/helm-chart/index.md "Pulumi's Helm Chart on Kubernetes template supports HCL as a language option (in addition to TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file's frontmatter explicitly lists hcl under template.languages alongside typescript, python, go, csharp, and yaml, and the meta_desc reads "Deploy a Helm chart to an existing Kubernetes cluster with Pulumi in TypeScri…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L18 in content/templates/kubernetes-application/helm-chart/index.md "The Helm Chart template's language list includes HCL." → ✅ verified (evidence: The file's front matter at line 18 explicitly lists - hcl under template.languages, and the meta_desc also states "TypeScript, Python, Go, C#, YAML, or HCL."; source: content/templates/kubernetes-application/helm-chart/index.md)
L58 in content/templates/kubernetes-application/helm-chart/index.md "The k8sNamespace configuration setting for the Helm Chart template defaults to nginx-ingress (for TypeScript, Python, Go, C#, and YAML languages)." (also L65) → ✅ verified (evidence: The file at content/templates/kubernetes-application/helm-chart/index.md contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that reads: "k8sNamespace: The name of the namespace to be created in your existing…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L65 in content/templates/kubernetes-application/helm-chart/index.md "The k8s_namespace configuration setting for the Helm Chart template (HCL language) defaults to nginx-ingress." → ✅ verified (evidence: The file at content/templates/kubernetes-application/helm-chart/index.md contains an HCL-specific choosable block that reads: "k8s_namespace : The name of the namespace to be created in your existing cluster. Defaults to nginx-ingress.…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L69 in content/templates/kubernetes-application/helm-chart/index.md "Helm Chart template configuration settings can be adjusted with the pulumi config set command." → ✅ verified (evidence: The file at line ~69 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/c…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L69 in content/templates/kubernetes-application/helm-chart/index.md "The stack configuration file is named Pulumi.dev.yaml by default." → ✅ verified (evidence: The file at line ~69 states: "by editing the stack configuration file directly (by default, Pulumi.dev.yaml)", directly confirming the claim that the stack configuration file is named Pulumi.dev.yaml by default.; source: content/templates/kubernetes-application/helm-chart/index.md)
L74 in content/templates/kubernetes-application/helm-chart/index.md "The CLI command to set the Helm Chart namespace configuration for TypeScript/Python/Go/C#/YAML is pulumi config set k8sNamespace my-namespace." → ✅ verified (evidence: The file at content/templates/kubernetes-application/helm-chart/index.md contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block with the exact command $ pulumi config set k8sNamespace my-namespace, confirming…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L83 in content/templates/kubernetes-application/helm-chart/index.md "The CLI command to set the Helm Chart namespace configuration for HCL is pulumi config set k8s_namespace my-namespace." → ✅ verified (evidence: The file at L83 (within the {{% choosable language hcl %}} block) shows exactly: $ pulumi config set k8s_namespace my-namespace, confirming the CLI command for setting the Helm Chart namespace configuration in HCL.; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L89 in content/templates/kubernetes-application/helm-chart/index.md "The Helm Chart template includes an example of passing values to the Helm chart in Pulumi code." → ✅ verified (evidence: The file at line ~89 states: "You can customize the Helm chart by passing values to it in your Pulumi code. An example of passing a few values to the chart is included in the template for reference." This directly confirms the claim that t…; source: repo:content/templates/kubernetes-application/helm-chart/index.md)
L6 in content/templates/kubernetes-application/web-application/index.md "Pulumi supports deploying a web application to an existing Kubernetes cluster using HCL (in addition to TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file's frontmatter at L6 (meta_desc) reads: "Deploy a web application to an existing Kubernetes cluster with Pulumi in TypeScript, Python, Go, C#, YAML, or HCL." The languages list in the template section also explicitly includes `…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L18 in content/templates/kubernetes-application/web-application/index.md "The Kubernetes web application template supports HCL as a language option." → ✅ verified (evidence: The file's front matter lists hcl under template.languages, and the meta_desc reads: "Deploy a web application to an existing Kubernetes cluster with Pulumi in TypeScript, Python, Go, C#, YAML, or HCL." The page body also contains HC…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L46 in content/templates/kubernetes-application/web-application/index.md "For TypeScript, Python, Go, C#, and YAML languages, the Kubernetes web application template exports stack output values named deploymentName and serviceName…" (also L54) → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.mdcontains a{{% choosable language "typescript,python,go,csharp,yaml" %}}block that lists exactlydeploymentNameandserviceName` as the exported stack ou…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L56 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exports stack output values named deployment_name and service_name." (also L64) → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.md contains an HCL-specific {{% choosable language hcl %}} block that lists exactly deployment_name and service_name as the exported stack output values: "d…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L58-59 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exports a stack output named deployment_name containing the name of the new Kubernetes Deployme…" → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.md contains an HCL-specific choosable block that reads: "deployment_name : The name of your new Kubernetes Deployment." — directly confirming the claim.; source: repo:content/templates/kubernetes-application/web-application/index.md)
L61-62 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exports a stack output named service_name containing the name of the new Kubernetes Service." → ✅ verified (evidence: The file content/templates/kubernetes-application/web-application/index.md contains an HCL-specific choosable block that lists service_name as a stack output: "service_name : The name of your new Kubernetes Service."; source: repo:content/templates/kubernetes-application/web-application/index.md)
L72 in content/templates/kubernetes-application/web-application/index.md "For TypeScript, Python, Go, C#, and YAML languages, the Kubernetes web application template exposes a configuration setting named namespace that defaults to…" (also L80) → ✅ verified (evidence: The index.md file (lines ~72-80) states under {{% choosable language "typescript,python,go,csharp,yaml" %}}: "namespace: The name of the namespace to be created in your existing cluster. Defaults to default." The upstream template sour…; source: repo:content/templates/kubernetes-application/web-application/index.md; gh api repos/pulumi/templates/contents/webapp-kubernetes-typescript/Pulumi.yaml)
L75 in content/templates/kubernetes-application/web-application/index.md "For TypeScript, Python, Go, C#, and YAML, the Kubernetes web application template's namespace configuration setting defaults to default." → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.md contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that states: "namespace: The name of the namespace to be created in your exist…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L77-78 in content/templates/kubernetes-application/web-application/index.md "For TypeScript, Python, Go, C#, and YAML languages, the Kubernetes web application template exposes a configuration setting named replicas that defaults to …" → ✅ verified (evidence: The index.md file at lines 77-78 explicitly states under {{% choosable language "typescript,python,go,csharp,yaml" %}}: "replicas: The number of replicated Pods to be created in your new Deployment. Defaults to 1`." The pulumi/templates…; source: repo:content/templates/kubernetes-application/web-application/index.md and gh search code --owner pulumi --repo pulumi/templates replicas)
L82 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exposes a configuration setting named k8s_namespace that defaults to webapp." (also L90) → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L84-85 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exposes a configuration setting named k8s_namespace for the namespace to be created in the exis…" → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.md contains an HCL-specific choosable block that reads: "k8s_namespace: The name of the namespace to be created in your existing cluster. Defaults to webapp." —…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L87-88 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template exposes a configuration setting named num_replicas for the number of replicated Pods to be crea…" → ✅ verified (evidence: The file's HCL-specific choosable block reads: "num_replicas: The number of replicated Pods to be created in your new Deployment. Defaults to 1." — exactly matching the claim.; source: repo:content/templates/kubernetes-application/web-application/index.md)
L92 in content/templates/kubernetes-application/web-application/index.md "All configuration settings for the Kubernetes web application template are optional and may be adjusted by editing the stack configuration file directly (by de…" → ✅ verified (evidence: The file at the relevant section reads: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set].…; source: repo:content/templates/kubernetes-application/web-application/index.md)
L103 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the Kubernetes web application template configuration setting for replica count is set via pulumi config set num_replicas 3." (also L110) → ✅ verified (evidence: The file at lines ~103–110 contains an HCL-specific {{% choosable language hcl %}} block with the exact command $ pulumi config set num_replicas 3, confirming the claim verbatim.; source: repo:content/templates/kubernetes-application/web-application/index.md)
L106 in content/templates/kubernetes-application/web-application/index.md "For the HCL language, the number of replicas in the Kubernetes web application template is set using pulumi config set num_replicas 3." → ✅ verified (evidence: The file at content/templates/kubernetes-application/web-application/index.md contains an HCL-specific choosable block that reads: $ pulumi config set num_replicas 3 followed by $ pulumi up, confirming the claim exactly.; source: repo:content/templates/kubernetes-application/web-application/index.md)
L6 in content/templates/kubernetes/aws/index.md "Pulumi's Kubernetes cluster on AWS template supports HCL as a language option (in addition to TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file content/templates/kubernetes/aws/index.md explicitly lists hcl in the languages array alongside typescript, python, go, csharp, and yaml, and the meta_desc reads: "Deploy a managed Kubernetes cluster on AWS with…; source: repo:content/templates/kubernetes/aws/index.md)
L48 in content/templates/kubernetes/aws/index.md "The Kubernetes on AWS template (TypeScript, Python, Go, C#, YAML) exports two stack outputs: kubeconfig (the cluster's kubeconfig file) and vpcId (the ID o…" (also L52) → ✅ verified (framing: strengthened — claim omits the HCL variant (which has different outputs: cluster_name, vpc_id, kubeconfig), but what it asserts for the five listed languages i…; evidence: The index.md file confirms: for TypeScript, Python, Go, C#, and YAML, the template exports kubeconfig ("The cluster's kubeconfig file") and vpcId ("The ID of the VPC that your cluster is running in"). The file also lists HCL as a suppo…; source: content/templates/kubernetes/aws/index.md)
L58-59 in content/templates/kubernetes/aws/index.md "The HCL Kubernetes on AWS template exports three stack outputs: cluster_name (the name of the EKS cluster), vpc_id (the ID of the VPC), and kubeconfig (t…" (also L65) → ✅ verified (evidence: The file's HCL choosable block explicitly lists three outputs: cluster_name ("The name of the EKS cluster"), vpc_id ("The ID of the VPC that your cluster is running in"), and kubeconfig ("The cluster's kubeconfig file, which you can…; source: content/templates/kubernetes/aws/index.md)
L61-62 in content/templates/kubernetes/aws/index.md "The HCL variant of the Kubernetes on AWS template exports a vpc_id stack output containing the ID of the VPC the cluster is running in." → ✅ verified (evidence: The file content/templates/kubernetes/aws/index.md contains a {{% choosable language hcl %}} block that explicitly lists vpc_id as a stack output: "vpc_id : The ID of the VPC that your cluster is running in."; source: repo:content/templates/kubernetes/aws/index.md)
L64-65 in content/templates/kubernetes/aws/index.md "The HCL variant of the Kubernetes on AWS template exports a kubeconfig stack output that can be used with kubectl to access and communicate with the cluste…" → ✅ verified (evidence: The HCL choosable block in the file explicitly lists kubeconfig as a stack output: "The cluster's kubeconfig file, which you can use with kubectl to access and communicate with your cluster." This directly confirms the claim.; source: repo:content/templates/kubernetes/aws/index.md)
L78 in content/templates/kubernetes/aws/index.md "The minClusterSize configuration setting for the Kubernetes on AWS template (TypeScript, Python, Go, C#, YAML) defaults to 3." → ✅ verified (evidence: The index.md file at L78 states "The minimum number of nodes to allow in the cluster. Defaults to 3." for minClusterSize. The actual template source code in pulumi/templates confirms this: Go uses minClusterSize = 3, C# uses `??…; source: gh search code --owner pulumi --repo pulumi/templates minClusterSize)
L84 in content/templates/kubernetes/aws/index.md "The desiredClusterSize configuration setting for the Kubernetes on AWS template (TypeScript, Python, Go, C#, YAML) defaults to 3." → ✅ verified (evidence: The index.md file states "desiredClusterSize: The desired number of nodes in the cluster. Defaults to 3." This is confirmed by the actual template source code in pulumi/templates: Go sets desiredClusterSize = 3, C# uses ?? 3, Pyt…; source: repo:content/templates/kubernetes/aws/index.md and gh search code --owner pulumi "desiredClusterSize" --repo pulumi/templates)
L87 in content/templates/kubernetes/aws/index.md "The eksNodeInstanceType configuration setting for the Kubernetes on AWS template defaults to t3.medium." → ✅ verified (evidence: The docs file at L87 states "eksNodeInstanceType: The EC2 instance type to use for the nodes. Defaults to t3.medium." This is confirmed by all language variants of the template in pulumi/templates, e.g. `kubernetes-aws-typescript/Pulumi.…; source: repo:content/templates/kubernetes/aws/index.md; gh search code --owner pulumi "eksNodeInstanceType" "t3.medium" --repo pulumi/templates)
L90 in content/templates/kubernetes/aws/index.md "The vpcNetworkCidr configuration setting for the Kubernetes on AWS template (TypeScript, Python, Go, C#, YAML) defaults to 10.0.0.0/16." → ✅ verified (evidence: The index.md file at L90 states "vpcNetworkCidr: The network CIDR to use for the VPC. Defaults to 10.0.0.0/16." This is confirmed by the actual template source code in pulumi/templates: TypeScript uses || "10.0.0.0/16", Python uses…; source: repo:content/templates/kubernetes/aws/index.md and gh search code --owner pulumi vpcNetworkCidr --repo pulumi/templates)
L97 in content/templates/kubernetes/aws/index.md "The HCL min_cluster_size configuration setting for the Kubernetes on AWS template defaults to 3." → ✅ verified (evidence: The file at the relevant line range explicitly states: "min_cluster_size : The minimum number of nodes to allow in the cluster. Defaults to 3." This is corroborated by the template source code where `min_cluster_size = config.get_int("mi…; source: repo:content/templates/kubernetes/aws/index.md (L97 area, HCL choosable block); gh search code pulumi/templates min_cluster_size)
L100 in content/templates/kubernetes/aws/index.md "The HCL max_cluster_size configuration setting for the Kubernetes on AWS template defaults to 6." → ✅ verified (evidence: The file at content/templates/kubernetes/aws/index.md explicitly states under the HCL choosable block: "max_cluster_size: The maximum number of nodes to allow in the cluster. Defaults to 6."; source: repo:content/templates/kubernetes/aws/index.md)
L103 in content/templates/kubernetes/aws/index.md "The HCL desired_cluster_size configuration setting for the Kubernetes on AWS template defaults to 3." → ✅ verified (evidence: The file content/templates/kubernetes/aws/index.md explicitly states under the HCL choosable block: "desired_cluster_size: The desired number of nodes in the cluster. Defaults to 3."; source: repo:content/templates/kubernetes/aws/index.md)
L106 in content/templates/kubernetes/aws/index.md "The HCL node_instance_type configuration setting for the Kubernetes on AWS template defaults to t3.medium." → ✅ verified (evidence: The file content/templates/kubernetes/aws/index.md in the HCL-specific choosable block explicitly states: "node_instance_type : The EC2 instance type to use for the nodes. Defaults to t3.medium."; source: repo:content/templates/kubernetes/aws/index.md)
L109 in content/templates/kubernetes/aws/index.md "The HCL vpc_network_cidr configuration setting for the Kubernetes on AWS template defaults to 10.0.0.0/16." → ✅ verified (evidence: The file's HCL choosable block explicitly states: "vpc_network_cidr : The network CIDR to use for the VPC. Defaults to 10.0.0.0/16."; source: repo:content/templates/kubernetes/aws/index.md)
L6 in content/templates/kubernetes/azure/index.md "Pulumi supports deploying a managed Kubernetes cluster on Azure with Azure Kubernetes Service (AKS) using TypeScript, Python, Go, C#, YAML, or HCL." → ✅ verified (evidence: The file's meta_desc (L6) reads: "Deploy a managed Kubernetes cluster on Azure with Pulumi and Azure Kubernetes Service (AKS) in TypeScript, Python, Go, C#, YAML, or HCL." The template's languages list also explicitly enumerates all si…; source: repo:content/templates/kubernetes/azure/index.md)
L18 in content/templates/kubernetes/azure/index.md "The Kubernetes Cluster on Azure template supports HCL as a language option." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md explicitly lists hcl under template.languages in the frontmatter, and the meta_desc reads "Deploy a managed Kubernetes cluster on Azure with Pulumi and Azure Kubernetes Service (…; source: repo:content/templates/kubernetes/azure/index.md)
L40 in content/templates/kubernetes/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, deploying the Kubernetes Cluster on Azure template requires supplying two values: mgmtGroupId and another va…" (also L45) → ✅ verified (framing: strengthened — claim says "mgmtGroupId and another value" without naming sshPubKey; source names both values explicitly, so the claim is a narrower (vaguer) bu…; evidence: The file confirms: "You must supply two values to deploy the cluster. You can input both through the new-project wizard: mgmtGroupId … sshPubKey …" under a {{% choosable language "typescript,python,go,csharp,yaml" %}} block, matching the…; source: content/templates/kubernetes/azure/index.md)
L54 in content/templates/kubernetes/azure/index.md "The HCL variant of the Kubernetes Cluster on Azure template requires no additional configuration and can be deployed immediately after project creation." → ✅ verified (evidence: The file at content/templates/kubernetes/azure/index.md contains the HCL choosable block: "The template requires no additional configuration. Once the new project is created, you can deploy it immediately with [pulumi up](/docs/iac/cli/c…; source: repo:content/templates/kubernetes/azure/index.md)
L66-67 in content/templates/kubernetes/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, the stack output rgname contains the name of the Azure Resource Group containing the Kubernetes cluster reso…" → ✅ verified (evidence: The file at lines ~66-67 contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that lists rgname with the description: "The name of the Azure Resource Group containing the Kubernetes cluster resources." This ex…; source: repo:content/templates/kubernetes/azure/index.md)
L75-76 in content/templates/kubernetes/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, the stack output kubeconfig contains the cluster's kubeconfig file, usable with kubectl to access and commun…" → ✅ verified (evidence: The file at lines 75-76 (within a {{% choosable language "typescript,python,go,csharp,yaml" %}} block) states: "kubeconfig: The cluster's kubeconfig file, which you can use with kubectl to access and communicate with your cluster." Thi…; source: repo:content/templates/kubernetes/azure/index.md)
L82-83 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template exports a stack output named cluster_name containing the name of the AKS cluster." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md contains an HCL-specific choosable block that explicitly lists: "cluster_name: The name of the AKS cluster." as a stack output exported by the HCL template.; source: repo:content/templates/kubernetes/azure/index.md)
L85-86 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template exports a stack output named kubeconfig containing the cluster's kubeconfig file, which can be used with kubect…" → ✅ verified (evidence: The HCL-specific choosable block in the file explicitly lists kubeconfigas a stack output: "The cluster's kubeconfig file, which you can use withkubectl` to access and communicate with your cluster."; source: repo:content/templates/kubernetes/azure/index.md)
L98-99 in content/templates/kubernetes/azure/index.md "The numWorkerNodes configuration setting for the Kubernetes Cluster on Azure template (TypeScript, Python, Go, C#, YAML) defaults to 3." → ✅ verified (evidence: The docs file at L98 states "numWorkerNodes: The number of nodes in your cluster. Defaults to 3." and the TypeScript template source confirms: const numWorkerNodes = projCfg.getNumber("numWorkerNodes") || 3;; source: repo:content/templates/kubernetes/azure/index.md and gh search code in pulumi/templates (kubernetes-azure-typescript/index.ts))
L107-108 in content/templates/kubernetes/azure/index.md "The nodeVmSize configuration setting for the Kubernetes Cluster on Azure template (TypeScript, Python, Go, C#, YAML) defaults to Standard_DS2_v2." → ✅ verified (evidence: The index.md file states "nodeVmSize: The VM instance type used to run your nodes. Defaults to Standard_DS2_v2." and the pulumi/templates repo confirms this default across all five languages (TypeScript, Python, Go, C#, YAML) with entrie…; source: repo:content/templates/kubernetes/azure/index.md; gh search code --owner pulumi "nodeVmSize" "Standard_DS2_v2" --repo pulumi/templates)
L114-115 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template has a location configuration setting that defaults to westus2." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md contains, within the {{% choosable language hcl %}} block: "location : The Azure region to deploy into. Defaults to westus2." — exactly matching the claim.; source: repo:content/templates/kubernetes/azure/index.md)
L117-118 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template has a node_count configuration setting that defaults to 3." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md under the HCL choosable block explicitly states: "node_count : The number of worker nodes in the cluster. Defaults to 3."; source: repo:content/templates/kubernetes/azure/index.md)
L120-121 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template has a dns_prefix configuration setting that defaults to pulumi." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md contains an HCL-specific configuration block that reads: "dns_prefix : The unique DNS prefix to use for the cluster. Defaults to pulumi." This directly confirms the claim.; source: repo:content/templates/kubernetes/azure/index.md)
L123-124 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template has a node_vm_size configuration setting that defaults to Standard_DS2_v2." → ✅ verified (evidence: The file content/templates/kubernetes/azure/index.md explicitly documents under the HCL choosable block: "node_vm_size: The VM size to use for worker nodes. Defaults to Standard_DS2_v2." The pulumi/templates repo also confirms `Standar…; source: repo:content/templates/kubernetes/azure/index.md (lines ~123-124); gh search code pulumi/templates "node_vm_size" "Standard_DS2_v2")
L128 in content/templates/kubernetes/azure/index.md "The stack configuration file is named Pulumi.dev.yaml by default." → ✅ verified (evidence: The file at content/templates/kubernetes/azure/index.md states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values wit…; source: repo:content/templates/kubernetes/azure/index.md)
L142 in content/templates/kubernetes/azure/index.md "The HCL Kubernetes Cluster on Azure template's worker node count can be changed using pulumi config set node_count 5." → ✅ verified (evidence: The file at content/templates/kubernetes/azure/index.md contains an HCL-specific choosable block that explicitly shows $ pulumi config set node_count 5 as the command to change the worker node count, and documents node_count as "The…; source: repo:content/templates/kubernetes/azure/index.md)
L6 in content/templates/kubernetes/gcp/index.md "The Kubernetes Cluster on Google Cloud template supports HCL as a language option (in addition to TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file at content/templates/kubernetes/gcp/index.md explicitly lists hcl in the languages array alongside typescript, python, go, csharp, and yaml, and the meta_desc reads "Deploy a managed Kubernetes cluster on Google…; source: repo:content/templates/kubernetes/gcp/index.md)
L18 in content/templates/kubernetes/gcp/index.md "The Kubernetes Cluster on Google Cloud template lists HCL as a supported language in its template configuration." → ✅ verified (evidence: The file's frontmatter at the template.languages section explicitly lists - hcl as one of the supported languages alongside typescript, python, go, csharp, and yaml.; source: content/templates/kubernetes/gcp/index.md)
L46 in content/templates/kubernetes/gcp/index.md "The HCL template for Kubernetes Cluster on GCP deploys into the active Google Cloud project read from gcloud credentials." → ✅ verified (evidence: The file at L46 (inside the HCL choosable block) reads: "The template deploys into your active Google Cloud project (read from your gcloud credentials) and defaults to the us-central1 region," which directly confirms the claim that the H…; source: repo:content/templates/kubernetes/gcp/index.md)
L77-78 in content/templates/kubernetes/gcp/index.md "The HCL variant of the Kubernetes Cluster template exports a network_name stack output containing the name of the VPC network containing the Kubernetes clust…" → ✅ verified (evidence: The file content/templates/kubernetes/gcp/index.md contains an HCL-specific choosable block that lists: "network_name : The name of the VPC network containing the Kubernetes cluster resources." — exactly matching the claim.; source: repo:content/templates/kubernetes/gcp/index.md)
L80-81 in content/templates/kubernetes/gcp/index.md "The HCL variant of the Kubernetes Cluster template exports a cluster_name stack output containing the name of the GKE cluster." → ✅ verified (evidence: The file content/templates/kubernetes/gcp/index.md contains a {{% choosable language hcl %}} block that explicitly lists cluster_name as a stack output: "cluster_name: The name of the GKE cluster."; source: repo:content/templates/kubernetes/gcp/index.md)
L83-84 in content/templates/kubernetes/gcp/index.md "The HCL template for Kubernetes Cluster on GCP exports a kubeconfig stack output containing the cluster's kubeconfig file, which can be used with kubectl t…" → ✅ verified (evidence: The HCL choosable block in the file explicitly lists kubeconfig as a stack output: "The cluster's kubeconfig file, which you can use with kubectl to access and communicate with your cluster."; source: content/templates/kubernetes/gcp/index.md)
L102-103 in content/templates/kubernetes/gcp/index.md "The non-HCL variants of the Kubernetes Cluster template expose a nodesPerZone configuration setting for the desired number of nodes per zone in the node pool…" → ✅ verified (evidence: The index.md file explicitly documents nodesPerZone: The desired number of nodes per zone in the node pool. Defaults to \1`.` under the non-HCL choosable block, and the template source code in pulumi/templates confirms this default (e.g…; source: repo:content/templates/kubernetes/gcp/index.md (L95-103); gh search code --owner pulumi "nodesPerZone" --repo pulumi/templates)
L109-110 in content/templates/kubernetes/gcp/index.md "The HCL variant of the Kubernetes Cluster template exposes a region configuration setting for the Google Cloud region to deploy into, defaulting to us-centr…" → ✅ verified (evidence: The file content/templates/kubernetes/gcp/index.mdcontains an HCL-specific choosable block that reads: "region\n: The Google Cloud region to deploy into. Defaults tous-central1`." — exactly matching the claim.; source: repo:content/templates/kubernetes/gcp/index.md)
L112-113 in content/templates/kubernetes/gcp/index.md "The HCL variant of the Kubernetes Cluster template exposes a nodes_per_zone configuration setting for the desired number of nodes per zone in the node pool,…" → ✅ verified (evidence: The file content/templates/kubernetes/gcp/index.md contains an HCL-specific choosable block that reads: "nodes_per_zone : The desired number of nodes per zone in the node pool. Defaults to 1." — exactly matching the claim.; source: repo:content/templates/kubernetes/gcp/index.md)
L117 in content/templates/kubernetes/gcp/index.md "All configuration settings for the Kubernetes Cluster template are optional and may be adjusted by editing the stack configuration file directly (by default, …" → ❌ contradicted (framing: narrowed — the file's own "all of these settings are optional" statement is contradicted by the same file's earlier requirement "You must supply an existing Go…; evidence: The file states "All of these settings are optional" but also explicitly says "You must supply an existing Google Cloud project ID to deploy the cluster" for TypeScript/Python/Go/C#/YAML languages — meaning gcp:project` is required, not o…; source: repo:content/templates/kubernetes/gcp/index.md)
L131 in content/templates/kubernetes/gcp/index.md "For the HCL variant, the nodes_per_zone configuration value can be set using pulumi config set nodes_per_zone 2." → ✅ verified (evidence: The file at content/templates/kubernetes/gcp/index.md contains an HCL-specific choosable block that explicitly shows $ pulumi config set nodes_per_zone 2 as the command to set the nodes_per_zone configuration value, matching the clai…; source: repo:content/templates/kubernetes/gcp/index.md)
L6 in content/templates/serverless-application/aws/index.md "The AWS Serverless Application template supports deployment in TypeScript, Python, Go, C#, YAML, and HCL." → ✅ verified (evidence: The file's frontmatter at template.languages lists exactly: typescript, python, go, csharp, yaml, hcl — and the meta_desc confirms "in TypeScript, Python, Go, C#, YAML, or HCL."; source: repo:content/templates/serverless-application/aws/index.md)
L6 in content/templates/serverless-application/aws/index.md "HCL is a supported language option for the AWS Serverless Application Pulumi template." (also L15, L18) → ✅ verified (evidence: The file at content/templates/serverless-application/aws/index.md explicitly lists hcl in the template.languages array (line 18) and the meta_desc (line 6) reads "in TypeScript, Python, Go, C#, YAML, or HCL", confirming HCL is a su…; source: repo:content/templates/serverless-application/aws/index.md)
L46-51 in content/templates/serverless-application/aws/index.md "For the TypeScript, Python, Go, C#, and YAML language variants of the AWS Serverless Application template, the stack output is named url and represents the H…" → ✅ verified (evidence: The file at lines 46-51 contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that documents: "url: The HTTP URL for the application." — exactly matching the claim that the stack output is named url and represe…; source: repo:content/templates/serverless-application/aws/index.md)
L53-61 in content/templates/serverless-application/aws/index.md "For the HCL language variant of the AWS Serverless Application template, the stack outputs are named site_url (the HTTP URL for the website) and api_url (t…" → ✅ verified (evidence: The file's HCL choosable block reads: "site_url: The HTTP URL for the website. api_url: The HTTP URL for the API endpoint." — exactly matching the claim.; source: repo:content/templates/serverless-application/aws/index.md)

github-actions · 2026-06-26T00:54:25Z

continued from previous comment

L69-77 in content/templates/serverless-application/aws/index.md "For the TypeScript, Python, Go, C#, and YAML language variants of the AWS Serverless Application template, the configuration setting code specifies the path…" (also L82) → ❌ contradicted (evidence: The actual template source code in pulumi/templates for all five language variants (TypeScript, Python, Go, C#, YAML) does NOT expose a code configuration setting. The Go template hardcodes pulumi.NewFileArchive("./function"), the C#…; source: gh api repos/pulumi/templates/contents/serverless-aws-go/main.go; gh api repos/pulumi/templates/contents/serverless-aws-csharp/Program.cs; gh api repos/pulumi/templates/contents/serverless-aws-yaml/Pulumi.yaml; gh api repos/pulumi/templates/contents/serverless-aws-python/Pulumi.yaml; gh api repos/pulumi/templates/contents/serverless-aws-typescript/Pulumi.yaml)
L72 in content/templates/serverless-application/aws/index.md "The /date path is a GET endpoint that retrieves the current time from the Lambda function (for TypeScript, Python, Go, C#, and YAML variants)." → ✅ verified (framing: strengthened — the claim correctly identifies the five language variants (TypeScript, Python, Go, C#, YAML) from the choosable block; the HCL variant also has…; evidence: The file at the relevant section contains exactly: "The /date path is a GET endpoint that retrieves the current time from the Lambda function." inside a {{% choosable language "typescript,python,go,csharp,yaml" %}} block, confirming th…; source: content/templates/serverless-application/aws/index.md)
L79-87 in content/templates/serverless-application/aws/index.md "For HCL, the AWS Serverless Application template exposes a configuration setting named app_path that specifies the path to the folder containing the Lambda f…" → ✅ verified (evidence: The file at content/templates/serverless-application/aws/index.md contains an HCL-specific choosable block that reads: "app_path: The path to the folder containing the Lambda function code. Defaults to the ./function folder included wi…; source: repo:content/templates/serverless-application/aws/index.md)
L82 in content/templates/serverless-application/aws/index.md "The /date path is a GET endpoint that retrieves the current time from the Lambda function (for the HCL variant)." → ❌ contradicted (framing: shifted — the claim says this description is "(for the HCL variant)" but the source shows the identical sentence appears in both the typescript/python/go/cshar…; evidence: The sentence "The /date path is a GET endpoint that retrieves the current time from the Lambda function." appears in BOTH the non-HCL choosable block (under path) and the HCL choosable block (under site_path). The claim incorrectly a…; source: repo:content/templates/serverless-application/aws/index.md)
L89 in content/templates/serverless-application/aws/index.md "By default, the AWS Serverless Application template deploys the website and function using files in the www and function folders bundled with the template." → ✅ verified (evidence: The file at content/templates/serverless-application/aws/index.md contains the exact sentence: "None of these settings is required; by default, the template deploys the website and function using the files in the www and function folde…; source: repo:content/templates/serverless-application/aws/index.md)
L95 in content/templates/serverless-application/aws/index.md "You can configure the stack to deploy from another folder by using pulumi config set to change the value of the website path setting." → ✅ verified (evidence: The file at line ~95 reads: "you can configure the stack to deploy from another folder on your machine by using pulumi config set to change the value of the website path setting" — matching the…; source: repo:content/templates/serverless-application/aws/index.md)
L97 in content/templates/serverless-application/aws/index.md "For the TypeScript, Python, Go, C#, and YAML language variants of the AWS Serverless Application template, the website path setting is configured via pulumi c…" (also L99-103) → ✅ verified (evidence: The index.md file at lines ~97-103 shows a {{% choosable language "typescript,python,go,csharp,yaml" %}}block containing$ pulumi config set path ../my-website/dist`, confirming that for those five language variants the website path se…; source: repo:content/templates/serverless-application/aws/index.md)
L106 in content/templates/serverless-application/aws/index.md "For the HCL language variant of the AWS Serverless Application template, the website path setting is configured via pulumi config set site_path <value>." (also L113) → ✅ verified (evidence: The file's HCL-specific choosable block explicitly shows: $ pulumi config set site_path ../my-website/dist and documents site_path as "The path to the folder containing the files of the website."; source: content/templates/serverless-application/aws/index.md)
L108-111 in content/templates/serverless-application/aws/index.md "For HCL, the website path is configured via pulumi config set site_path ../my-website/dist." → ✅ verified (evidence: The file at content/templates/serverless-application/aws/index.md contains an HCL-specific {{% choosable language hcl %}} block showing exactly $ pulumi config set site_path ../my-website/dist as the command to configure the website…; source: repo:content/templates/serverless-application/aws/index.md)
L6 in content/templates/serverless-application/azure/index.md "The Azure Serverless Application template supports HCL as a language option, in addition to TypeScript, Python, Go, C#, and YAML." → ✅ verified (evidence: The file's front matter at line 6 (meta_desc) reads "Deploy a serverless application on Azure with Pulumi, Azure Functions, and Azure Blob Storage in TypeScript, Python, Go, C#, YAML, or HCL." and the languages list explicitly includes…; source: repo:content/templates/serverless-application/azure/index.md)
L18 in content/templates/serverless-application/azure/index.md "The Azure Serverless Application template lists HCL as a supported language in its template configuration." → ✅ verified (evidence: The file's template configuration block explicitly lists - hcl as one of the supported languages alongside typescript, python, go, csharp, and yaml.; source: repo:content/templates/serverless-application/azure/index.md)
L48-52 in content/templates/serverless-application/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the Azure Serverless Application template exports a stack output named apiURL containing the HTTP URL of the server…" → ✅ verified (evidence: The index.md file at L48-52 explicitly lists apiURL as a stack output for {{% choosable language "typescript,python,go,csharp,yaml" %}} with description "The HTTP URL of the serverless function endpoint." This is confirmed by the actua…; source: repo:content/templates/serverless-application/azure/index.md; gh search code --owner pulumi --repo pulumi/templates apiURL)
L56 in content/templates/serverless-application/azure/index.md "For the HCL language variant of the Azure Serverless Application template, the stack output for the serverless function endpoint URL is named api_url (not a…" (also L64) → ✅ verified (evidence: The file explicitly shows a {{% choosable language hcl %}}block listingapi_urlas "The HTTP URL of the serverless function endpoint," while the non-HCL block usesapiURL` instead.; source: content/templates/serverless-application/azure/index.md)
L58-59 in content/templates/serverless-application/azure/index.md "For HCL, the Azure Serverless Application template exports a stack output named site_url containing the HTTP URL of the static website." → ✅ verified (evidence: The file content/templates/serverless-application/azure/index.md explicitly states under the HCL choosable block: "site_url : The HTTP URL of the static website." This directly matches the claim.; source: repo:content/templates/serverless-application/azure/index.md)
L61-62 in content/templates/serverless-application/azure/index.md "For HCL, the Azure Serverless Application template exports a stack output named api_url containing the HTTP URL of the serverless function endpoint." → ✅ verified (evidence: The file content/templates/serverless-application/azure/index.md contains an HCL-specific choosable block that reads: "api_url : The HTTP URL of the serverless function endpoint." — exactly matching the claim.; source: repo:content/templates/serverless-application/azure/index.md)
L66 in content/templates/serverless-application/azure/index.md "Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed website URL, for example, c…" → ➖ not-a-claim (evidence: The text at L66 is a descriptive prose sentence in the PR author's own documentation page explaining how stack output values can be used. It is a faithful description of the page's own design/content, not a falsifiable third-party-attribut…; source: repo:content/templates/serverless-application/azure/index.md)
L71 in content/templates/serverless-application/azure/index.md "Running open $(pulumi stack output siteURL) opens the deployed website from the command line (for TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file at L71 shows open $(pulumi stack output siteURL) inside a {{% choosable language "typescript,python,go,csharp,yaml" %}} block, confirming the command applies exactly to those five languages. HCL uses a separate block with `sit…; source: repo:content/templates/serverless-application/azure/index.md)
L76 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the deployed website can be opened from the command line using open $(pulumi stack output site_url)." (also L82) → ✅ verified (evidence: The file at lines ~76–82 contains an HCL-specific {{% choosable language hcl %}} block with exactly: $ open $(pulumi stack output site_url), confirming the claim verbatim.; source: repo:content/templates/serverless-application/azure/index.md)
L79 in content/templates/serverless-application/azure/index.md "Running open $(pulumi stack output site_url) opens the deployed website from the command line for HCL." → ✅ verified (evidence: The file at L79 (within the HCL choosable block) contains exactly: $ open $(pulumi stack output site_url), confirming the claim that this command opens the deployed website from the command line for HCL.; source: repo:content/templates/serverless-application/azure/index.md)
L88 in content/templates/serverless-application/azure/index.md "For the non-HCL language variants (TypeScript, Python, Go, C#, YAML) of the Azure Serverless Application template, the sitePath configuration setting default…" (also L99-101) → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md explicitly states within the {{% choosable language "typescript,python,go,csharp,yaml" %}} block: "sitePath: The path to the folder containing the files of the website…; source: repo:content/templates/serverless-application/azure/index.md)
L91 in content/templates/serverless-application/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the sitePath configuration setting defaults to www." → ✅ verified (evidence: The file at the relevant section contains: sitePath\n: The path to the folder containing the files of the website. Defaults to \www`, which is the folder included with the template.inside a{{% choosable language "typescript,python,g…; source: repo:content/templates/serverless-application/azure/index.md)
L104 in content/templates/serverless-application/azure/index.md "For the HCL language variant of the Azure Serverless Application template, the location configuration setting specifies the Azure region to deploy into and d…" (also L121) → ✅ verified (evidence: The file content/templates/serverless-application/azure/index.md in the HCL-specific {{% choosable language hcl %}} block explicitly states: "location: The Azure region to deploy into. Defaults to WestUS." — exactly matching the clai…; source: repo:content/templates/serverless-application/azure/index.md)
L107 in content/templates/serverless-application/azure/index.md "For HCL, the Azure Serverless Application template exposes a location configuration setting that defaults to WestUS." → ✅ verified (evidence: The file's HCL choosable block explicitly states: "location: The Azure region to deploy into. Defaults to WestUS." — exactly matching the claim.; source: content/templates/serverless-application/azure/index.md)
L109-110 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the site_path configuration setting specifies the path to the folder containing website files and defaults to ./www." → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md contains, within the {{% choosable language hcl %}} block: "site_path: The path to the folder containing the files of the website. Defaults to ./www, which is the…; source: repo:content/templates/serverless-application/azure/index.md)
L112-113 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the app_path configuration setting specifies the path to the folder containing serverless functions to be deployed and defaults…" → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md contains, within the {{% choosable language hcl %}} block: "app_path: The path to the folder containing the serverless functions to be deployed. Defaults to ./app, whi…; source: repo:content/templates/serverless-application/azure/index.md)
L115-116 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the index_document configuration setting specifies the file to use for top-level pages and defaults to index.html." → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md contains, within the {{% choosable language hcl %}} block: "index_document: The file to use for top-level pages. Defaults to index.html." — exactly matching the cl…; source: repo:content/templates/serverless-application/azure/index.md)
L118-119 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the error_document configuration setting specifies the file to use for error pages and defaults to error.html." → ✅ verified (evidence: The file's HCL-specific {{% choosable language hcl %}} block explicitly states: "error_document: The file to use for error pages. Defaults to error.html." — exactly matching the claim.; source: repo:content/templates/serverless-application/azure/index.md)
L123 in content/templates/serverless-application/azure/index.md "All configuration settings for the Azure Serverless Application template are optional and may be adjusted by editing the stack configuration file directly (by…" → ✅ verified (evidence: The file at L123 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/cli/c…; source: repo:content/templates/serverless-application/azure/index.md)
L128 in content/templates/serverless-application/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the site path is configured using pulumi config set sitePath." → ✅ verified (evidence: The file at line ~128 contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block with the bash snippet $ pulumi config set sitePath ../my-existing-website/build, confirming that for those five languages the config k…; source: repo:content/templates/serverless-application/azure/index.md)
L134 in content/templates/serverless-application/azure/index.md "For the HCL language variant, the site path configuration can be set using pulumi config set site_path ../my-existing-website/build." (also L141) → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md contains an HCL-specific choosable block with exactly: $ pulumi config set site_path ../my-existing-website/build followed by $ pulumi up, confirming the claim verba…; source: repo:content/templates/serverless-application/azure/index.md)
L137 in content/templates/serverless-application/azure/index.md "For HCL, the site path is configured using pulumi config set site_path." → ✅ verified (evidence: The file at content/templates/serverless-application/azure/index.md contains an HCL-specific choosable block showing $ pulumi config set site_path ../my-existing-website/build, confirming that for HCL the site path is configured using…; source: repo:content/templates/serverless-application/azure/index.md)
L6 in content/templates/serverless-application/gcp/index.md "The Google Cloud Serverless Application Pulumi template supports HCL as a language option, in addition to TypeScript, Python, Go, C#, and YAML." (also L18) → ✅ verified (evidence: The file's meta_desc (L6) reads "in TypeScript, Python, Go, C#, YAML, or HCL" and the languages list (L11–18) explicitly includes typescript, python, go, csharp, yaml, and hcl, confirming HCL is supported alongside the othe…; source: repo:content/templates/serverless-application/gcp/index.md)
L18 in content/templates/serverless-application/gcp/index.md "The Google Cloud Serverless Application template lists HCL as a supported language in its template configuration." → ✅ verified (evidence: The file's frontmatter template.languages list at line 18 explicitly includes - hcl, confirming HCL is listed as a supported language in the template configuration.; source: repo:content/templates/serverless-application/gcp/index.md)
L52-53 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML languages, the stack output for the static website URL is named siteURL." → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that lists siteURL as "The HTTP URL of the static website." The HCL variant uses `site_u…; source: repo:content/templates/serverless-application/gcp/index.md)
L55-56 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML languages, the stack output for the serverless function endpoint URL is named apiURL." → ✅ verified (evidence: The file explicitly shows within the {{% choosable language "typescript,python,go,csharp,yaml" %}} block: "apiURL\n: The HTTP URL of the serverless function endpoint." — confirming the stack output is named apiURL for those five langua…; source: repo:content/templates/serverless-application/gcp/index.md)
L62-63 in content/templates/serverless-application/gcp/index.md "For the HCL language, the stack output for the static website URL is named site_url." → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md contains an HCL-specific choosable block that reads: "site_url : The HTTP URL of the static website." — confirming the stack output for the static website URL is named `si…; source: repo:content/templates/serverless-application/gcp/index.md)
L65-66 in content/templates/serverless-application/gcp/index.md "For the HCL language, the stack output for the serverless function endpoint URL is named api_url." → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md contains an HCL-specific choosable block that reads: "api_url\n: The HTTP URL of the serverless function endpoint." — confirming the stack output is named api_url for HC…; source: repo:content/templates/serverless-application/gcp/index.md)
L70 in content/templates/serverless-application/gcp/index.md "Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed site URL, for example, can…" → ➖ not-a-claim (evidence: The text is an explanatory prose sentence authored by the PR author describing how Pulumi stack output values can be used — it is a faithful description of the author's own documentation design and template behavior, not a falsifiable thir…; source: repo:content/templates/serverless-application/gcp/index.md)
L75 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML variants, the stack output key for the static website URL is named siteURL (camelCase), accessible via pulumi stack…" → ✅ verified (evidence: All five GCP serverless template variants in pulumi/templates use siteURL as the stack output key: TypeScript (export const siteURL = ...), Python ("siteURL",), Go (ctx.Export("siteURL", ...)), C# (["siteURL"] = ...), and YAML (…; source: gh search code --owner pulumi --repo pulumi/templates "siteURL")
L83 in content/templates/serverless-application/gcp/index.md "For the HCL variant, the stack output key for the static website URL is named site_url (snake_case), accessible via pulumi stack output site_url." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L90 in content/templates/serverless-application/gcp/index.md "The serverless template exposes configuration settings that can be customized." → ✅ verified (evidence: The file at L90 explicitly states: "Projects created with the serverless template expose the following configuration settings:" and lists multiple configurable settings (sitePath, appPath, indexDocument, errorDocument, etc.).; source: content/templates/serverless-application/gcp/index.md)
L94-95 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML languages, the sitePath configuration setting defaults to www, which is the name and relative path of the folder i…" → ✅ verified (evidence: The file's {{% choosable language "typescript,python,go,csharp,yaml" %}} block states: "sitePath: The path to the folder containing the files of the website. Defaults to www, which is the name (and relative path) of the folder included…; source: repo:content/templates/serverless-application/gcp/index.md)
L103-104 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML languages, the errorDocument configuration setting defaults to error.html." → ✅ verified (evidence: The file at lines ~103-104 (within the {{% choosable language "typescript,python,go,csharp,yaml" %}} block) states: "errorDocument: The file to use for error pages. Defaults to error.html." — exactly matching the claim for those five l…; source: repo:content/templates/serverless-application/gcp/index.md)
L111 in content/templates/serverless-application/gcp/index.md "For the HCL language, the region configuration setting specifies the Google Cloud region to deploy into and defaults to us-central1." → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md in the HCL choosable block states: "region: The Google Cloud region to deploy into. Defaults to us-central1." — exactly matching the claim.; source: repo:content/templates/serverless-application/gcp/index.md)
L113-114 in content/templates/serverless-application/gcp/index.md "For the HCL language, the site_path configuration setting specifies the path to the folder containing the website files and defaults to ./www." → ✅ verified (evidence: The file at L113-114 states under the HCL choosable block: "site_path: The path to the folder containing the files of the website. Defaults to ./www, which is the relative path of the folder included with the template."; source: content/templates/serverless-application/gcp/index.md)
L116-117 in content/templates/serverless-application/gcp/index.md "For the HCL language, the app_path configuration setting specifies the path to the folder containing the serverless functions to be deployed and defaults to…" → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md contains, within the {{% choosable language hcl %}} block: "app_path: The path to the folder containing the serverless functions to be deployed. Defaults to ./app, whi…; source: repo:content/templates/serverless-application/gcp/index.md)
L119-120 in content/templates/serverless-application/gcp/index.md "For the HCL variant of the Google Cloud Serverless Application template, the index_document configuration setting defaults to index.html." → ✅ verified (evidence: The file at content/templates/serverless-application/gcp/index.md explicitly states in the HCL choosable block: "index_document: The file to use for top-level pages. Defaults to index.html."; source: repo:content/templates/serverless-application/gcp/index.md)
L122-123 in content/templates/serverless-application/gcp/index.md "For the HCL variant of the Google Cloud Serverless Application template, the error_document configuration setting defaults to error.html." → ✅ verified (evidence: The HCL choosable block in content/templates/serverless-application/gcp/index.md explicitly states: "error_document: The file to use for error pages. Defaults to error.html."; source: repo:content/templates/serverless-application/gcp/index.md)
L127 in content/templates/serverless-application/gcp/index.md "Stack configuration settings can be adjusted by editing the stack configuration file directly or by using pulumi config set." → ✅ verified (evidence: The file at L127 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/cli/c…; source: repo:content/templates/serverless-application/gcp/index.md)
L127 in content/templates/serverless-application/gcp/index.md "Configuration settings can be changed with the pulumi config set command." → ✅ verified (evidence: The file at line ~127 explicitly states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set]…; source: repo:content/templates/serverless-application/gcp/index.md)
L132 in content/templates/serverless-application/gcp/index.md "For TypeScript, Python, Go, C#, and YAML languages, the command to set the site path configuration is pulumi config set sitePath ../my-existing-website/build." → ✅ verified (evidence: The file contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block with exactly $ pulumi config set sitePath ../my-existing-website/build as the command, matching the claim precisely.; source: repo:content/templates/serverless-application/gcp/index.md)
L141 in content/templates/serverless-application/gcp/index.md "For the HCL language, the command to set the site path configuration is pulumi config set site_path ../my-existing-website/build." → ✅ verified (evidence: The file contains an HCL-specific choosable block with exactly: $ pulumi config set site_path ../my-existing-website/build, confirming the claim verbatim.; source: repo:content/templates/serverless-application/gcp/index.md)
L18 in content/templates/static-website/aws/index.md "The Static Website AWS template supports HCL as a language option." → ✅ verified (evidence: The file content/templates/static-website/aws/index.md explicitly lists hcl in the template.languages frontmatter array (alongside typescript, python, go, csharp, yaml), and the body of the page contains HCL-specific content blocks t…; source: repo:content/templates/static-website/aws/index.md)
L48-52 in content/templates/static-website/aws/index.md "When the deployment completes, the stack output cdnHostname is the provider-assigned hostname of the CloudFront CDN, useful for creating CNAME records to ass…" (also L58-62) → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md contains within a {{% choosable language "typescript,python,go,csharp,yaml" %}} block: "cdnHostname\n: The provider-assigned hostname of the CloudFront CDN. Useful for creating…; source: repo:content/templates/static-website/aws/index.md)
L58-59 in content/templates/static-website/aws/index.md "For the HCL language variant, the stack output cdn_url is the fully-qualified HTTPS URL of the CloudFront CDN." → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md contains an HCL-specific choosable block that reads: "cdn_url\n: The fully-qualified HTTPS URL of the CloudFront CDN." — exactly matching the claim.; source: repo:content/templates/static-website/aws/index.md)
L61-62 in content/templates/static-website/aws/index.md "For the HCL language variant, the stack output cdn_hostname is the provider-assigned hostname of the CloudFront CDN, useful for creating CNAME records to ass…" → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md contains an HCL-specific choosable block that reads: "cdn_hostname: The provider-assigned hostname of the CloudFront CDN. Useful for creating CNAME records to associate custom d…; source: repo:content/templates/static-website/aws/index.md)
L66 in content/templates/static-website/aws/index.md "Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed CDN URL, for example, can b…" → ➖ not-a-claim (evidence: The text at L66 ("Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed CDN URL, for example, can be used from the command line to open the newly deployed websit…; source: repo:content/templates/static-website/aws/index.md)
L71 in content/templates/static-website/aws/index.md "The command open $(pulumi stack output cdnURL) can be used to open the deployed website in a browser (for typescript, python, go, csharp, yaml languages)." (also L79) → ✅ verified (evidence: The file at lines ~71-79 shows open $(pulumi stack output cdnURL) inside a {{% choosable language "typescript,python,go,csharp,yaml" %}} block, exactly matching the claim's listed languages. The HCL variant uses cdn_url instead.; source: repo:content/templates/static-website/aws/index.md)
L79 in content/templates/static-website/aws/index.md "The command open $(pulumi stack output cdn_url) can be used to open the deployed website in a browser for the HCL language variant." → ✅ verified (evidence: The file contains an HCL-specific {{% choosable language hcl %}} block with exactly the command: $ open $(pulumi stack output cdn_url), confirming the claim that this command is used for the HCL language variant.; source: repo:content/templates/static-website/aws/index.md)
L91 in content/templates/static-website/aws/index.md "For HCL, the path configuration setting defaults to ./www, whereas for other languages (TypeScript, Python, Go, C#, YAML) it defaults to www." (also L104) → ✅ verified (evidence: The index.md file at the specified lines explicitly states for typescript,python,go,csharp,yaml: "Defaults to www", and for hcl: "Defaults to ./www, which is the name (and relative path) of the folder included with the template." T…; source: repo:content/templates/static-website/aws/index.md)
L96-97 in content/templates/static-website/aws/index.md "The errorDocument configuration setting for the Static Website template (typescript, python, go, csharp, yaml) defaults to error.html." → ✅ verified (evidence: The docs file at L96-97 states "errorDocument: The file to use for error pages. Defaults to error.html." for the typescript/python/go/csharp/yaml choosable block. The authoritative template source (`static-website-aws-typescript/Pulumi.y…; source: gh api repos/pulumi/templates/contents/static-website-aws-typescript/Pulumi.yaml)
L104 in content/templates/static-website/aws/index.md "The path configuration setting for the Static Website template HCL variant defaults to ./www." → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md contains an HCL-specific block that reads: "path: The path to the folder containing the files of the website. Defaults to ./www, which is the name (and relative path) of the fol…; source: repo:content/templates/static-website/aws/index.md)
L107 in content/templates/static-website/aws/index.md "The index_document configuration setting for the HCL variant of the Static Website template defaults to index.html." → ✅ verified (evidence: The file content/templates/static-website/aws/index.md contains an HCL-specific choosable block that states: "index_document: The file to use for top-level pages. Defaults to index.html."; source: repo:content/templates/static-website/aws/index.md)
L110 in content/templates/static-website/aws/index.md "The error_document configuration setting for the HCL variant of the Static Website template defaults to error.html." → ✅ verified (evidence: The file content/templates/static-website/aws/index.md in the HCL choosable block explicitly states: "error_document: The file to use for error pages. Defaults to error.html."; source: repo:content/templates/static-website/aws/index.md)
L114 in content/templates/static-website/aws/index.md "The stack configuration file is named Pulumi.dev.yaml by default." → ✅ verified (evidence: The file at line ~114 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set]..." — exac…; source: repo:content/templates/static-website/aws/index.md)
L127 in content/templates/static-website/aws/index.md "By default, the generated program configures the CloudFront CDN to cache files for 600 seconds (10 minutes)." → ✅ verified (evidence: The official Pulumi static website AWS template page states: "By default, the generated program configures the CloudFront CDN to cache files for 600 seconds (10 minutes), which may or may not be the best fit for your project or stack."; source: https://www.pulumi.com/templates/static-website/aws/)
L213-221 in content/templates/static-website/aws/index.md "In the HCL template, the CloudFront distribution resource is named aws_cloudfront_distribution with label cdn, and the default/max/min TTL fields are defa…" → ✅ verified (framing: strengthened — the claim specifies the label cdn, which is a user-defined HCL label and not constrained by the provider schema; the provider schema confirms…; evidence: The hashicorp/aws Terraform provider's aws_cloudfront_distributionresource usesdefault_cache_behaviorwithdefault_ttl, max_ttl, and min_ttl` fields, as confirmed by multiple authoritative sources. Issue Fix some titles and meta descriptions #1472 explicitly referen…; source: Allow for default cloudfront TTLs hashicorp/terraform-provider-aws#1472)
L336 in content/templates/static-website/aws/index.md "For typescript, python, go, csharp, yaml variants, the ACM certificate resource is added just above the aws.cloudfront.Distribution declaration." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L342 in content/templates/static-website/aws/index.md "For the HCL variant, the ACM certificate resource is added just above the aws_cloudfront_distribution resource." → ✅ verified (framing: strengthened — the source describes the pattern for all variants; the claim narrows it to the HCL variant specifically, which is a valid subset.; evidence: The Pulumi static website AWS template docs state: "just above the aws.cloudfront.Distribution declaration, add these lines to provision and validate a new SSL/TLS certificate with AWS Certificate Manager (ACM)." The HCL variant uses `aws_…; source: https://www.pulumi.com/templates/static-website/aws/)
L557 in content/templates/static-website/aws/index.md "ACM certificates for CloudFront must be created in the us-east-1 region." → ✅ verified (evidence: AWS official CloudFront documentation states: "To use a certificate in AWS Certificate Manager (ACM) to require HTTPS between viewers and CloudFront, make sure you request (or import) the certificate in the US East (N. Virginia) Region (us…; source: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/cnames-and-https-requirements.html)
L567 in content/templates/static-website/aws/index.md "In the HCL variant, the ACM certificate uses DNS as the validation method (validation_method = 'DNS')." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L584 in content/templates/static-website/aws/index.md "In the HCL variant, the Route 53 certificate validation record has a TTL of 60 seconds." → ✅ verified (evidence: The Pulumi static website AWS template page and related docs consistently show the Route 53 certificate validation record with ttl: 60 across all language variants, including the YAML/HCL variant: "ttl: 60" appears in the aws:route53:Rec…; source: https://www.pulumi.com/templates/static-website/aws/ and https://www.pulumi.com/guides/how-to/aws-acm-certificate/)
L592 in content/templates/static-website/aws/index.md "For typescript, python, go, csharp, yaml variants, the CloudFront configuration is extended by adding an aliases argument and adjusting viewerCertificate t…" → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L598 in content/templates/static-website/aws/index.md "For the HCL variant, the CloudFront configuration is extended by adding an aliases argument and adjusting the viewer_certificate block to use the newly pro…" → ✅ verified (framing: strengthened — the source describes the general concept using camelCase (viewerCertificate); the claim correctly narrows it to the HCL variant using snake_ca…; evidence: The docs file at content/templates/static-website/aws/index.md contains the passage: "Extend the CloudFront configuration to handle requests for the new domain by adding an aliases argument to the CDN configuration and adjusting `viewerC…; source: pulumi/docs:content/templates/static-website/aws/index.md (gh search code result))
L705-708 in content/templates/static-website/aws/index.md "In the HCL variant, the viewer_certificate block sets cloudfront_default_certificate = false, acm_certificate_arn to the provisioned certificate ARN, and…" → ✅ verified (evidence: The hashicorp/aws Terraform provider's aws_cloudfront_distribution resource supports a viewer_certificate block with exactly these attributes. A GitHub issue shows: "cloudfront_default_certificate = false, `acm_certificate_arn = aws_…; source: [Bug]: InvalidViewerCertificate message when creating CloudFront distribution hashicorp/terraform-provider-aws#40260)
L714 in content/templates/static-website/aws/index.md "A Route 53 A record is added to create a DNS record pointing to the CloudFront CDN." → 🤷 unverifiable (evidence: verification did not converge within 8 turns)
L904-906 in content/templates/static-website/aws/index.md "In the HCL variant, the stack output domain_url is exported with the value https://${local.domain_name}." → 🤷 unverifiable (evidence: Web searches found no public source containing the specific HCL template code with a domain_url stack output valued https://${local.domain_name} for the Pulumi AWS static website template. Standard Pulumi AWS static website templates u…; source: WebSearch ran query "pulumi templates static-website aws HCL domain_url local.domain_name github"; top results didn't address the claim; intuition: The output name domain_url and the local.domain_name interpolation pattern are atypical for Pulumi's own HCL varian…)
L922 in content/templates/static-website/aws/index.md "The command open $(pulumi stack output domainURL) can be used to browse to the website using the custom domain (for typescript, python, go, csharp, yaml lang…" (also L930) → ✅ verified (evidence: The file content/templates/static-website/aws/index.md contains $ open $(pulumi stack output domainURL) (confirmed by gh search code), and the file's choosable blocks consistently use `{{% choosable language "typescript,python,go,csh…; source: repo:content/templates/static-website/aws/index.md; gh search code --owner pulumi --repo pulumi/docs "stack output domainURL")
L930 in content/templates/static-website/aws/index.md "The command open $(pulumi stack output domain_url) can be used to browse to the website using the custom domain for the HCL language variant." → ❌ contradicted (evidence: The file's HCL choosable block shows open $(pulumi stack output cdn_url) for browsing the deployed website — not domain_url. A search for domain_url in the file returns no results, meaning no such output or command exists in this fil…; source: repo:content/templates/static-website/aws/index.md (read_file) + gh search code returning no results for domain_url in that path)
L939 in content/templates/static-website/aws/index.md "For third-party DNS, the exported stack output for the CDN hostname is cdnHostname for TypeScript/Python/Go/C#/YAML and cdn_hostname for HCL, and can be us…" (also L949) → ✅ verified (evidence: The file explicitly documents: for TypeScript/Python/Go/C#/YAML — "cdnHostname: The provider-assigned hostname of the CloudFront CDN. Useful for creating CNAME records to associate custom domains." and for HCL — "cdn_hostname: The provid…; source: repo:content/templates/static-website/aws/index.md)
L939 in content/templates/static-website/aws/index.md "For typescript, python, go, csharp, yaml variants, the exported stack output cdnHostname can be used to create a CNAME record with a third-party DNS provider." → ✅ verified (framing: strengthened — source says "Useful for creating CNAME records to associate custom domains" (general); claim narrows this to "with a third-party DNS provider"…; evidence: The file confirms that for {{% choosable language "typescript,python,go,csharp,yaml" %}}, the stack output cdnHostname is described as "The provider-assigned hostname of the CloudFront CDN. Useful for creating CNAME records to associ…; source: repo:content/templates/static-website/aws/index.md)
L942 in content/templates/static-website/aws/index.md "The command pulumi stack output cdnHostname retrieves the CDN hostname value (for typescript, python, go, csharp, yaml languages)." → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md explicitly defines cdnHostname as a stack output under {{% choosable language "typescript,python,go,csharp,yaml" %}}: "cdnHostname: The provider-assigned hostname of the Cloud…; source: repo:content/templates/static-website/aws/index.md)
L952 in content/templates/static-website/aws/index.md "The command pulumi stack output cdn_hostname retrieves the CDN hostname value for the HCL language variant." → ✅ verified (evidence: The file explicitly defines cdn_hostname as the HCL-specific stack output for the CDN hostname: "cdn_hostname: The provider-assigned hostname of the CloudFront CDN. Useful for creating CNAME records to associate custom domains." within…; source: repo:content/templates/static-website/aws/index.md)
L957 in content/templates/static-website/aws/index.md "Pulumi supports many third-party DNS providers, all of which are available in the Pulumi Registry and accompanied by examples." → 🤷 unverifiable (framing: narrowed — claim asserts all DNS providers in the Registry are accompanied by examples; no source supports the universal "all" framing, making this an overclai…; evidence: (escalated from pass1) The Pulumi Registry does list multiple third-party DNS providers (e.g., DNSimple, GCP DNS, Azure DNS) and many include examples, but no authoritative source confirms that all DNS providers in the Registry are "acco…; source: WebSearch ran query "Pulumi Registry third-party DNS providers examples accompanied"; top results showed individual DNS provider pages but no source confirming all are accompanied by examples.; intuition: The "all of which are accompanied by examples" sub-clause is suspiciously absolute — Registry packages vary widely in d…)
L959 in content/templates/static-website/aws/index.md "DNSimple is listed as a supported third-party DNS provider available in the Pulumi Registry." → ✅ verified (evidence: The file at content/templates/static-website/aws/index.md lists DNSimple as a third-party DNS option: "using a third-party service like DNSimple or Google Cloud DNS." The Pulumi Re…; source: repo:content/templates/static-website/aws/index.md; gh search code --owner pulumi dnsimple --repo pulumi/registry)
L6 in content/templates/static-website/azure/index.md "The Azure Static Website template supports HCL as a language option, in addition to TypeScript, Python, Go, C#, and YAML." → ✅ verified (evidence: The file's front matter explicitly lists hcl in the languages array alongside typescript, python, go, csharp, and yaml, and the meta_desc reads: "Deploy a static website on Azure with Pulumi, Azure Blob Storage, and Azure C…; source: content/templates/static-website/azure/index.md)
L18 in content/templates/static-website/azure/index.md "The Azure Static Website template includes HCL as a supported language option." → ✅ verified (evidence: The file's front matter explicitly lists hcl under template.languages alongside typescript, python, go, csharp, and yaml, and the meta_desc reads: "Deploy a static website on Azure with Pulumi, Azure Blob Storage, and Azure CDN in Ty…; source: repo:content/templates/static-website/azure/index.md)
L46 in content/templates/static-website/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the Azure Static Website template exports a stack output named originHostname containing the provider-assigned host…" → ✅ verified (evidence: The index.md documents originHostname as "The provider-assigned hostname of the Azure Blob Storage container" within a {{% choosable language "typescript,python,go,csharp,yaml" %}} block. The pulumi/templates repo confirms all five…; source: gh search code --owner pulumi "originHostname" --repo pulumi/templates; gh api repos/pulumi/templates/contents/static-website-azure-typescript/index.ts)
L48-49 in content/templates/static-website/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, the Azure Static Website template exports an originHostname stack output representing the provider-assigne…" → ✅ verified (evidence: The index.md file at L48-49 documents originHostname as "The provider-assigned hostname of the Azure Blob Storage container" under a {{% choosable language "typescript,python,go,csharp,yaml" %}} block. The actual template source files…; source: repo:content/templates/static-website/azure/index.md; gh api repos/pulumi/templates/contents/static-website-azure-typescript/index.ts; gh search code --owner pulumi --repo pulumi/templates originHostname)
L57-58 in content/templates/static-website/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, the Azure Static Website template exports a cdnURL stack output representing the fully-qualified HTTPS URL…" → ✅ verified (evidence: The TypeScript template exports export const cdnURL = pulumi.interpolate\https://${endpoint.hostName}`and the YAML template outputscdnURL: https://${endpoint.hostName}. The index.md documents cdnURL` as "The fully-qualified HTTPS…; source: gh api repos/pulumi/templates/contents/static-website-azure-typescript/index.ts; gh api repos/pulumi/templates/contents/static-website-azure-yaml/Pulumi.yaml; repo:content/templates/static-website/azure/index.md)
L64-65 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exports an origin_url stack output representing the fully-qualified HTTP URL of the storage container en…" → ✅ verified (evidence: The index.md file's HCL-specific choosable block explicitly lists origin_url with the description "The fully-qualified HTTP URL of the storage container endpoint." as a stack output for the HCL variant.; source: repo:content/templates/static-website/azure/index.md)
L67-68 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exports an origin_hostname stack output representing the provider-assigned hostname of the Azure Blob St…" → ✅ verified (evidence: The index.md file explicitly documents, within the {{% choosable language hcl %}} block: "origin_hostname: The provider-assigned hostname of the Azure Blob Storage container." — exactly matching the claim.; source: repo:content/templates/static-website/azure/index.md)
L70-71 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exports a cdn_url stack output representing the fully-qualified HTTPS URL of the Azure CDN." → ✅ verified (evidence: The file content/templates/static-website/azure/index.md explicitly documents under the HCL choosable block: "cdn_url: The fully-qualified HTTPS URL of the Azure CDN." — exactly matching the claim.; source: repo:content/templates/static-website/azure/index.md)
L73-74 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exports a cdn_hostname stack output representing the provider-assigned hostname of the Azure CDN, descri…" → ✅ verified (evidence: The file at content/templates/static-website/azure/index.md contains, within the {{% choosable language hcl %}} block: "cdn_hostname\n: The provider-assigned hostname of the Azure CDN. Useful for creating CNAME records to associate c…; source: repo:content/templates/static-website/azure/index.md)
L74 in content/templates/static-website/azure/index.md "The cdn_hostname output is useful for creating CNAME records to associate custom domains." → ✅ verified (evidence: The file at content/templates/static-website/azure/index.md states under the HCL block: "cdn_hostname: The provider-assigned hostname of the Azure CDN. Useful for creating CNAME records to associate custom domains." This is an exact ma…; source: repo:content/templates/static-website/azure/index.md)
L78 in content/templates/static-website/azure/index.md "Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed CDN URL, for example, can b…" → ➖ not-a-claim (evidence: The line at L78 is a general descriptive sentence about how stack output values can be used ("most commonly as inputs for other stacks or related cloud resources"), followed by an illustrative example of opening the CDN URL in a browser. T…; source: repo:content/templates/static-website/azure/index.md)
L83 in content/templates/static-website/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the deployed website's CDN URL can be opened from the command line using open $(pulumi stack output cdnURL)." → ✅ verified (evidence: The file contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block with exactly $ open $(pulumi stack output cdnURL), matching the claim precisely. The HCL variant uses cdn_url instead.; source: content/templates/static-website/azure/index.md)
L91 in content/templates/static-website/azure/index.md "For the HCL variant, the CDN URL stack output is named cdn_url and can be retrieved with pulumi stack output cdn_url." → ✅ verified (evidence: The file content/templates/static-website/azure/index.md explicitly documents in the HCL choosable block: cdn_url as a stack output ("The fully-qualified HTTPS URL of the Azure CDN"), and the bash snippet `$ open $(pulumi stack output…; source: repo:content/templates/static-website/azure/index.md)
L102-103 in content/templates/static-website/azure/index.md "For TypeScript, Python, Go, C#, and YAML variants, the path configuration setting defaults to www (the name and relative path of the folder included with t…" → ✅ verified (evidence: The file at L102-103 (under the {{% choosable language "typescript,python,go,csharp,yaml" %}} block) states: "path: The path to the folder containing the files of the website. Defaults to www, which is the name (and relative path) of t…; source: content/templates/static-website/azure/index.md)
L115-116 in content/templates/static-website/azure/index.md "For HCL, the Azure Static Website template exposes a location configuration setting that specifies the Azure region to deploy into, defaulting to WestUS." → ✅ verified (evidence: The file content/templates/static-website/azure/index.md contains, within the {{% choosable language hcl %}} block: "location\n: The Azure region to deploy into. Defaults to WestUS." — exactly matching the claim.; source: repo:content/templates/static-website/azure/index.md)
L118-119 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exposes a path configuration setting that defaults to ./www." → ✅ verified (evidence: The file content/templates/static-website/azure/index.md contains, within the HCL choosable block: "path: The path to the folder containing the files of the website. Defaults to ./www, which is the name (and relative path) of the folde…; source: repo:content/templates/static-website/azure/index.md)
L121-122 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exposes an index_document configuration setting that defaults to index.html." → ✅ verified (evidence: The file at content/templates/static-website/azure/index.md explicitly documents under the {{% choosable language hcl %}} block: "index_document: The file to use for top-level pages. Defaults to index.html."; source: repo:content/templates/static-website/azure/index.md)
L124-125 in content/templates/static-website/azure/index.md "The HCL variant of the Azure Static Website template exposes an error_document configuration setting that defaults to error.html." → ✅ verified (evidence: The file's HCL-specific {{% choosable language hcl %}} block explicitly states: "error_document: The file to use for error pages. Defaults to error.html." — directly confirming the claim.; source: repo:content/templates/static-website/azure/index.md)
L129 in content/templates/static-website/azure/index.md "The default stack configuration file for the Azure Static Website template is named Pulumi.dev.yaml." → ✅ verified (evidence: The file at content/templates/static-website/azure/index.md states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values…; source: repo:content/templates/static-website/azure/index.md)
L6 in content/templates/static-website/gcp/index.md "The Google Cloud Static Website Pulumi template supports HCL as a language option (in addition to TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file's front matter lists languages: [typescript, python, go, csharp, yaml, hcl] and the meta_desc reads "Deploy a static website on Google Cloud with Pulumi, Cloud Storage, and Cloud CDN in TypeScript, Python, Go, C#, YAML, or HCL…; source: repo:content/templates/static-website/gcp/index.md)
L18 in content/templates/static-website/gcp/index.md "The Google Cloud Static Website template lists HCL as one of its supported languages." → ✅ verified (evidence: The file's front matter lists hcl under template.languages (alongside typescript, python, go, csharp, yaml), and the meta_desc reads: "Deploy a static website on Google Cloud with Pulumi, Cloud Storage, and Cloud CDN in TypeScript, P…; source: repo:content/templates/static-website/gcp/index.md)
L48-58 in content/templates/static-website/gcp/index.md "For TypeScript, Python, Go, C#, and YAML, the Google Cloud Static Website template exports a stack output named originHostname containing the provider-assign…" → ✅ verified (evidence: All five GCP static website templates (TypeScript, Python, Go, C#, YAML) export originHostname as a stack output. For example: export const originHostname = pulumi.interpolate\storage.googleapis.com/${bucket.name}`(TypeScript),ctx…; source: gh search code --owner pulumi --repo pulumi/templates originHostname; also repo:content/templates/static-website/gcp/index.md)
L57-58 in content/templates/static-website/gcp/index.md "The cdnURL stack output is the fully-qualified HTTPS URL of the Google Cloud CDN (for TypeScript, Python, Go, C#, and YAML)." → ❌ contradicted (framing: shifted — the doc claims HTTPS but the actual stack output is HTTP for all GCP language variants; evidence: The index.md describes cdnURL as "The fully-qualified HTTPS URL of the Google Cloud CDN," but all five GCP template programs use http:// not https://: e.g., TypeScript exports `http://${ip.address}`, Python exports `f"http://{a…; source: gh search code --owner pulumi --repo pulumi/templates cdnURL)
L64-65 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exports a stack output named origin_url containing the fully-qualified HTTP URL of the storage bucket endpo…" → ✅ verified (evidence: The file content/templates/static-website/gcp/index.md explicitly documents under the HCL choosable block: "origin_url\n: The fully-qualified HTTP URL of the storage bucket endpoint." — exactly matching the claim.; source: repo:content/templates/static-website/gcp/index.md)
L67-68 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exports a stack output named origin_hostname containing the provider-assigned hostname of the Google Cloud…" → ✅ verified (evidence: The file content/templates/static-website/gcp/index.md contains an HCL-specific choosable block that lists origin_hostname with the description: "The provider-assigned hostname of the Google Cloud Storage bucket."; source: repo:content/templates/static-website/gcp/index.md)
L70-71 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exports a stack output named cdn_url containing the fully-qualified HTTPS URL of the Google Cloud CDN." → ✅ verified (evidence: The file content/templates/static-website/gcp/index.md explicitly documents the HCL-specific stack output: "cdn_url : The fully-qualified HTTPS URL of the Google Cloud CDN." under the {{% choosable language hcl %}} block.; source: repo:content/templates/static-website/gcp/index.md)

github-actions · 2026-06-26T00:54:26Z

continued from previous comment

L73-74 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exports a stack output named cdn_hostname containing the provider-assigned hostname of the Google Cloud CDN…" → ✅ verified (evidence: The file's HCL choosable block explicitly lists cdn_hostname as a stack output: "The provider-assigned hostname of the Google Cloud CDN. Useful for creating CNAME records to associate custom domains." — matching the claim exactly.; source: content/templates/static-website/gcp/index.md)
L74 in content/templates/static-website/gcp/index.md "The cdn_hostname stack output is useful for creating CNAME records to associate custom domains." → ✅ verified (evidence: The file explicitly states under the HCL choosable block: "cdn_hostname : The provider-assigned hostname of the Google Cloud CDN. Useful for creating CNAME records to associate custom domains."; source: repo:content/templates/static-website/gcp/index.md)
L78 in content/templates/static-website/gcp/index.md "Output values like these are useful in many ways, most commonly as inputs for other stacks or related cloud resources. The computed CDN URL, for example, can b…" → ➖ not-a-claim (evidence: The text at L78 is a descriptive narrative sentence authored by the PR author explaining how stack output values can be used — it is a faithful description of the PR author's own template design, not a falsifiable assertion about a third-p…; source: repo:content/templates/static-website/gcp/index.md)
L83 in content/templates/static-website/gcp/index.md "Running open $(pulumi stack output cdnURL) from the command line opens the newly deployed website (for TypeScript, Python, Go, C#, and YAML)." → ✅ verified (evidence: The file at L83 shows open $(pulumi stack output cdnURL) inside a {{% choosable language "typescript,python,go,csharp,yaml" %}} block, confirming it opens the deployed website and applies exactly to TypeScript, Python, Go, C#, and YAML…; source: repo:content/templates/static-website/gcp/index.md)
L91 in content/templates/static-website/gcp/index.md "Running open $(pulumi stack output cdn_url) from the command line opens the newly deployed website for the HCL template." → ✅ verified (evidence: The file at content/templates/static-website/gcp/index.md contains an HCL-specific choosable block with exactly $ open $(pulumi stack output cdn_url), preceded by the text "can be used from the command line to open the newly deployed web…; source: repo:content/templates/static-website/gcp/index.md)
L102-103 in content/templates/static-website/gcp/index.md "For TypeScript, Python, Go, C#, and YAML, the Google Cloud Static Website template's path configuration setting defaults to www." → ✅ verified (evidence: The file at L102-103 reads: "path\n: The path to the folder containing the files of the website. Defaults to www, which is the name (and relative path) of the folder included with the template." — this is inside a `{{% choosable language…; source: repo:content/templates/static-website/gcp/index.md)
L108-109 in content/templates/static-website/gcp/index.md "For TypeScript, Python, Go, C#, and YAML, the Google Cloud Static Website template's errorDocument configuration setting defaults to error.html." → ✅ verified (evidence: The file at content/templates/static-website/gcp/index.md contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that explicitly states: "errorDocument: The file to use for error pages. Defaults to error.html."; source: repo:content/templates/static-website/gcp/index.md)
L115-116 in content/templates/static-website/gcp/index.md "The path configuration setting for the HCL Google Cloud Static Website template defaults to ./www." → ✅ verified (evidence: The file content/templates/static-website/gcp/index.md under the HCL choosable block states: "path: The path to the folder containing the files of the website. Defaults to ./www, which is the relative path of the folder included with t…; source: repo:content/templates/static-website/gcp/index.md)
L118-119 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exposes a configuration setting named index_document that specifies the file to use for top-level pages, de…" → ✅ verified (evidence: The file's HCL-specific {{% choosable language hcl %}} block explicitly states: "index_document: The file to use for top-level pages. Defaults to index.html." — exactly matching the claim.; source: content/templates/static-website/gcp/index.md)
L121-122 in content/templates/static-website/gcp/index.md "For HCL, the Google Cloud Static Website template exposes a configuration setting named error_document that specifies the file to use for error pages, defaul…" → ✅ verified (evidence: The HCL-specific section of the file contains: "error_document\n: The file to use for error pages. Defaults to error.html." — exactly matching the claim's description of the configuration setting name, purpose, and default value.; source: content/templates/static-website/gcp/index.md)
L126 in content/templates/static-website/gcp/index.md "The stack configuration file is named Pulumi.dev.yaml by default." → ✅ verified (evidence: The file at line 126 states: "by editing the stack configuration file directly (by default, Pulumi.dev.yaml)". This matches standard Pulumi behavior where the default stack name is dev, producing a config file named Pulumi.dev.yaml.; source: repo:content/templates/static-website/gcp/index.md)
L126 in content/templates/static-website/gcp/index.md "Configuration settings for the Google Cloud Static Website template can be changed using pulumi config set." → ✅ verified (evidence: The file at line ~126 states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/…; source: repo:content/templates/static-website/gcp/index.md)
L126 in content/templates/static-website/gcp/index.md "The pulumi config set command documentation is located at /docs/iac/cli/commands/pulumi_config_set." → ✅ verified (evidence: The file content/docs/iac/cli/commands/pulumi_config_set.md exists in the repo with title "pulumi config set | CLI commands", and the template file at L126 links to it as [pulumi config set](/docs/iac/cli/commands/pulumi_config_set),…; source: repo:content/docs/iac/cli/commands/pulumi_config_set.md)
L6 in content/templates/virtual-machine/aws/index.md "The Virtual Machine on AWS template supports deployment with Pulumi in HCL (in addition to TypeScript, Python, Go, C#, and YAML)." (also L18) → ✅ verified (evidence: The file's meta_desc (L6) reads "Deploy an Amazon EC2 virtual machine on AWS running Amazon Linux 2023 with Pulumi in TypeScript, Python, Go, C#, YAML, or HCL." and the languages list (L18) explicitly includes hcl alongside `typescri…; source: repo:content/templates/virtual-machine/aws/index.md)
L67-68 in content/templates/virtual-machine/aws/index.md "For TypeScript, Python, Go, C#, and YAML, the EC2 instance type configuration key is named instanceType and defaults to t3.micro." → ✅ verified (evidence: All five language templates in pulumi/templates confirm the key is instanceType defaulting to t3.micro (e.g., const instanceType = config.get("instanceType") || "t3.micro" in TypeScript, default: t3.micro in each language's `Pulumi…; source: gh search code --owner pulumi "instanceType" "t3.micro" --repo pulumi/templates)
L70-71 in content/templates/virtual-machine/aws/index.md "For TypeScript, Python, Go, C#, and YAML, the VPC network CIDR configuration key is named vpcNetworkCidr and defaults to 10.0.0.0/16." → ✅ verified (evidence: The index.md file at L70-71 states vpcNetworkCidr defaults to 10.0.0.0/16 under a {{% choosable language "typescript,python,go,csharp,yaml" %}} block. The pulumi/templates repo confirms this across all five languages: e.g., `const vp…; source: gh search code --owner pulumi "vpcNetworkCidr" --repo pulumi/templates; repo:content/templates/virtual-machine/aws/index.md)
L77-78 in content/templates/virtual-machine/aws/index.md "The HCL instance_type configuration setting for the Virtual Machine template defaults to t3.micro." → ✅ verified (evidence: The file at content/templates/virtual-machine/aws/index.md contains the HCL choosable block: "instance_type\n: The EC2 instance type to use for the VM. Defaults to t3.micro."; source: repo:content/templates/virtual-machine/aws/index.md)
L80-81 in content/templates/virtual-machine/aws/index.md "The HCL vpc_network_cidr configuration setting for the Virtual Machine template defaults to 10.0.0.0/16." → ✅ verified (evidence: The file content/templates/virtual-machine/aws/index.md explicitly states under the HCL choosable block: "vpc_network_cidr: The network CIDR to use for the VPC. Defaults to 10.0.0.0/16." The pulumi/templates repo also confirms the same…; source: repo:content/templates/virtual-machine/aws/index.md; gh search code --owner pulumi "vpc_network_cidr" --repo pulumi/templates)
L83-84 in content/templates/virtual-machine/aws/index.md "The HCL variant of the Virtual Machine on AWS template has a service_port configuration option that the other language variants (TypeScript, Python, Go, C#,…" → 🤷 unverifiable (evidence: The official Pulumi AWS VM template page lists only TypeScript, Python, Go, C#, and YAML variants with instanceType and vpcNetworkCidr config options — no HCL variant or service_port option appears anywhere in the public docs or temp…; source: WebSearch ran query "pulumi vm-aws-hcl template service_port github pulumi/templates"; top results didn't address the claim; intuition: No HCL variant of the AWS VM template appears to exist in the public pulumi/templates repo; the claim may be based on a…)
L88 in content/templates/virtual-machine/aws/index.md "Stack configuration settings can be adjusted by editing the stack configuration file directly, which defaults to Pulumi.dev.yaml." → ✅ verified (evidence: The file at content/templates/virtual-machine/aws/index.md states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values…; source: repo:content/templates/virtual-machine/aws/index.md)
L88 in content/templates/virtual-machine/aws/index.md "Configuration settings for the Virtual Machine template can be changed using the pulumi config set command." → ✅ verified (evidence: The file explicitly states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/cl…; source: repo:content/templates/virtual-machine/aws/index.md)
L6 in content/templates/virtual-machine/azure/index.md "Pulumi's Azure Virtual Machine template supports HCL as a language option, in addition to TypeScript, Python, Go, C#, and YAML." → ✅ verified (evidence: The file's frontmatter explicitly lists hcl in the languages array alongside typescript, python, go, csharp, and yaml, and the meta_desc reads: "Deploy an Azure virtual machine with Pulumi and Azure Virtual Machines in Type…; source: content/templates/virtual-machine/azure/index.md)
L46-57 in content/templates/virtual-machine/azure/index.md "For TypeScript, Python, Go, C#, and YAML languages, the Azure Virtual Machine template exports stack outputs: ip (IP address of the VM), hostname (provider-ass…" → ✅ verified (evidence: The file's {{% choosable language "typescript,python,go,csharp,yaml" %}} block lists exactly three stack outputs: ip ("The IP address of the virtual machine"), hostname ("The provider-assigned hostname of the virtual machine"), and `…; source: repo:content/templates/virtual-machine/azure/index.md)
L59-73 in content/templates/virtual-machine/azure/index.md "For the HCL language variant, the Azure Virtual Machine template exports stack outputs: ip (IP address of the VM), hostname (provider-assigned hostname), url (…" → ✅ verified (evidence: The file at L59-73 (within the {{% choosable language hcl %}} block) lists exactly four stack outputs for HCL: ip (IP address of the VM), hostname (provider-assigned hostname), url (fully-qualified HTTP URL of the HTTP server), and…; source: repo:content/templates/virtual-machine/azure/index.md)
L85-104 in content/templates/virtual-machine/azure/index.md "For TypeScript, Python, Go, C#, and YAML, the Azure Virtual Machine template exposes an 'adminUsername' configuration setting for the user account to create on…" → ✅ verified (evidence: The index.md file contains a {{% choosable language "typescript,python,go,csharp,yaml" %}} block that documents: "adminUsername: The user account to create on the VM. Defaults to pulumiuser." — exactly matching the claim for all five l…; source: repo:content/templates/virtual-machine/azure/index.md)
L107 in content/templates/virtual-machine/azure/index.md "The HCL variant of the Azure Virtual Machine template exposes the following configuration settings: location (Azure location, defaults to WestUS2), admin_use…" (also L127) → ✅ verified (evidence: The HCL choosable block in the file lists exactly these six settings with matching descriptions and defaults: location (defaults to WestUS2), admin_username (defaults to pulumiuser), vm_name (defaults to my-server), vm_size (…; source: repo:content/templates/virtual-machine/azure/index.md)
L109-110 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes a 'location' configuration setting for the Azure location to deploy into, defaulting to 'WestUS2'." → ✅ verified (evidence: The file content/templates/virtual-machine/azure/index.md contains, within the {{% choosable language hcl %}} block: "location : The Azure location to deploy into. Defaults to WestUS2." — exactly matching the claim.; source: repo:content/templates/virtual-machine/azure/index.md)
L112-113 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes an 'admin_username' configuration setting for the user account to create on the VM, defaulting to 'pulumius…" → ✅ verified (evidence: The file at content/templates/virtual-machine/azure/index.md contains, within the {{% choosable language hcl %}} block: "admin_username\n: The user account to create on the VM. Defaults to pulumiuser." — exactly matching the claim.; source: repo:content/templates/virtual-machine/azure/index.md)
L115-116 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes a 'vm_name' configuration setting for the DNS hostname prefix to use for the VM, defaulting to 'my-server'." → ✅ verified (evidence: The file at content/templates/virtual-machine/azure/index.md contains an HCL-specific choosable block that reads: "vm_name : The DNS hostname prefix to use for the VM. Defaults to my-server." — exactly matching the claim.; source: repo:content/templates/virtual-machine/azure/index.md)
L118-119 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes a 'vm_size' configuration setting for the machine size to use for the VM, defaulting to 'Standard_A1_v2'." → ✅ verified (evidence: The file at content/templates/virtual-machine/azure/index.md in the HCL choosable block explicitly states: "vm_size : The machine size to use for the VM. Defaults to Standard_A1_v2."; source: repo:content/templates/virtual-machine/azure/index.md)
L121-122 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes an 'os_image' configuration setting for the Azure image reference (publisher:offer:sku:version) to use for…" → ✅ verified (evidence: The file at content/templates/virtual-machine/azure/index.md contains exactly: "os_image\n: The Azure image reference (publisher:offer:sku:version) to use for the VM. Defaults to Debian:debian-11:11:latest." under the `{{% choosable la…; source: repo:content/templates/virtual-machine/azure/index.md)
L124-125 in content/templates/virtual-machine/azure/index.md "For HCL, the Azure Virtual Machine template exposes a 'service_port' configuration setting for the HTTP service port to expose on the VM, defaulting to 80." → ✅ verified (evidence: The file at content/templates/virtual-machine/azure/index.md contains an HCL-specific {{% choosable language hcl %}} block that explicitly lists: "service_port: The HTTP service port to expose on the VM. Defaults to 80."; source: repo:content/templates/virtual-machine/azure/index.md)
L129 in content/templates/virtual-machine/azure/index.md "The Azure Virtual Machine template's stack configuration file is named 'Pulumi.dev.yaml' by default." → ✅ verified (evidence: Line 129 of the file states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set]..."; source: repo:content/templates/virtual-machine/azure/index.md)
L6 in content/templates/virtual-machine/gcp/index.md "Pulumi's Virtual Machine on Google Cloud template supports deployment in TypeScript, Python, Go, C#, YAML, and HCL." → ✅ verified (evidence: The file's meta_desc states "Deploy a Google Cloud virtual machine with Pulumi and Compute Engine in TypeScript, Python, Go, C#, YAML, or HCL." and the languages list in the template frontmatter explicitly includes typescript, `pytho…; source: repo:content/templates/virtual-machine/gcp/index.md)
L18 in content/templates/virtual-machine/gcp/index.md "The Virtual Machine on Google Cloud template includes HCL as a supported language option." → ✅ verified (evidence: The file's front matter explicitly lists hcl in the languages array: - typescript, - python, - go, - csharp, - yaml, - hcl. The meta_desc also states "TypeScript, Python, Go, C#, YAML, or HCL."; source: content/templates/virtual-machine/gcp/index.md)
L61-62 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Virtual Machine on Google Cloud template exports a name stack output representing the name of the virtual machine instance." → ✅ verified (evidence: The file content/templates/virtual-machine/gcp/index.md contains an HCL-specific choosable block that lists name as a stack output: "name\n: The name of the virtual machine instance." This directly matches the claim.; source: repo:content/templates/virtual-machine/gcp/index.md)
L64-65 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Virtual Machine on Google Cloud template exports an ip stack output representing the IP address of the virtual machine." → ✅ verified (evidence: The file at content/templates/virtual-machine/gcp/index.md contains an HCL-specific {{% choosable language hcl %}} block that lists ip as a stack output: "ip\n: The IP address of the virtual machine."; source: repo:content/templates/virtual-machine/gcp/index.md)
L67-68 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Virtual Machine on Google Cloud template exports a url stack output representing the fully-qualified HTTP URL of the HTTP server runni…" → ✅ verified (evidence: The index.md file's HCL-specific choosable block explicitly lists url as a stack output: "url: The fully-qualified HTTP URL of the HTTP server running on the virtual machine."; source: repo:content/templates/virtual-machine/gcp/index.md)
L85 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Google Cloud virtual machine template has a 'machine_type' configuration setting for the Compute Engine machine type, defaulting to 'e2-…" (also L100-101) → ✅ verified (evidence: The file at lines 100-101 (within the {{% choosable language hcl %}} block) explicitly states: "machine_type\n: The Compute Engine machine type to use for the VM. Defaults to e2-micro."; source: content/templates/virtual-machine/gcp/index.md)
L85 in content/templates/virtual-machine/gcp/index.md "The Compute Engine machine type configuration setting ('machineType') for the non-HCL Google Cloud virtual machine template defaults to 'e2-micro'." → ✅ verified (evidence: The file at the relevant line range explicitly states under the non-HCL choosable block: "machineType: The Compute Engine machine type to use for the VM. Defaults to e2-micro." The HCL section uses machine_type (snake_case), confirming…; source: repo:content/templates/virtual-machine/gcp/index.md)
L93-94 in content/templates/virtual-machine/gcp/index.md "The HTTP service port configuration setting ('servicePort') for the non-HCL Google Cloud virtual machine template defaults to '80'." → ✅ verified (evidence: The file at content/templates/virtual-machine/gcp/index.md explicitly states under the {{% choosable language "typescript,python,go,csharp,yaml" %}} block: "servicePort: The HTTP service port to expose on the VM. Defaults to 80." Thi…; source: repo:content/templates/virtual-machine/gcp/index.md)
L103-104 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Google Cloud virtual machine template has an 'os_image' configuration setting for the OS image type, defaulting to 'debian-11'." → ✅ verified (evidence: The file at content/templates/virtual-machine/gcp/index.md contains an HCL-specific choosable block that reads: "os_image: The OS image type to use for the VM. Defaults to debian-11." — exactly matching the claim.; source: repo:content/templates/virtual-machine/gcp/index.md)
L106-107 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Google Cloud virtual machine template has an 'instance_tag' configuration setting for the tag to apply to the VM instance, defaulting to…" → ✅ verified (evidence: The file at content/templates/virtual-machine/gcp/index.md under the {{% choosable language hcl %}} block explicitly states: "instance_tag : The tag to apply to the VM instance. Defaults to webserver."; source: repo:content/templates/virtual-machine/gcp/index.md)
L109-110 in content/templates/virtual-machine/gcp/index.md "The HCL variant of the Google Cloud virtual machine template has a 'service_port' configuration setting for the HTTP service port to expose on the VM, defaulti…" → ✅ verified (evidence: The file's HCL-specific choosable block explicitly lists: "service_port: The HTTP service port to expose on the VM. Defaults to 80." — exactly matching the claim.; source: repo:content/templates/virtual-machine/gcp/index.md)
L114 in content/templates/virtual-machine/gcp/index.md "Configuration values for the Virtual Machine on Google Cloud template can be changed using the pulumi config set command." → ✅ verified (evidence: The file explicitly states: "All of these settings are optional and may be adjusted either by editing the stack configuration file directly (by default, Pulumi.dev.yaml) or by changing their values with [pulumi config set](/docs/iac/cl…; source: repo:content/templates/virtual-machine/gcp/index.md)

🚨 Outstanding in this PR

No outstanding issues found in this PR.

⚠️ Low-confidence

Review each and resolve as appropriate — these don't block the PR.

[L957] content/templates/static-website/aws/index.md — "Pulumi supports many third-party DNS providers, all of which are available in the Pulumi Registry and accompanied by examples." — verdict: unverifiable. This sentence is pre-existing (this PR only wrapped the surrounding content in choosable blocks), but the universal "all of which are … accompanied by examples" is hard to support — Registry packages vary in documentation depth, and verification found no source confirming every third-party DNS provider ships an example. Author check: consider softening to something like "many of which are accompanied by examples."
[L83-84] content/templates/virtual-machine/aws/index.md — "The HCL variant of the Virtual Machine on AWS template has a service_port configuration option that the other language variants (TypeScript, Python, Go, C#,…" — verdict: unverifiable. The new HCL block documents a service_port setting (default 80) that the other-language blocks don't list. Verification couldn't independently confirm that the AWS VM HCL template actually exposes service_port while the other variants omit it (the HCL template isn't yet discoverable in the public pulumi/templates repo). Author check: please confirm the HCL template has a service_port setting and that its absence from the other-language blocks is intentional rather than an omission.

📋 Triaged verifier findings

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

[L64] content/templates/container-service/azure/index.md — "For the TypeScript, Python, Go, and C# variants of the Container Service on Azure template, the configuration settings include appPath, containerPort, and…" — Spurious: The page lists cpu and memory in both the non-HCL and the HCL configuration blocks, so they're not HCL-specific. The contradiction came from comparing a shortened form of the claim that read those two settings as HCL-only; the page itself is correct.
[L82] content/templates/serverless-application/aws/index.md — "The /date path is a GET endpoint that retrieves the current time from the Lambda function (for the HCL variant)." — Spurious: The /date endpoint description appears in both the non-HCL and the HCL blocks; the page documents both variants correctly. The contradiction came from a paraphrase that attributed the sentence to the HCL variant alone.
[L930] content/templates/static-website/aws/index.md — "The command open $(pulumi stack output domain_url) can be used to browse to the website using the custom domain for the HCL language variant." — Spurious: The HCL custom-domain walkthrough exports an output "domain_url" (valued https://${local.domain_name}) a few steps above this command, so pulumi stack output domain_url is correct for the HCL variant. The check searched the earlier stack-outputs section (which uses cdn_url) and missed the domain_url output added later in the same file.
[L82] content/templates/kubernetes-application/web-application/index.md — "For the HCL language, the Kubernetes web application template exposes a configuration setting named k8s_namespace that defaults to webapp." — Mis-sourced: The same setting is confirmed elsewhere in the file — the HCL k8s_namespace default of webapp is verified at L84-85. Verification ran out of turns on this duplicate.
[L83] content/templates/serverless-application/gcp/index.md — "For the HCL variant, the stack output key for the static website URL is named site_url (snake_case), accessible via pulumi stack output site_url." — Mis-sourced: Duplicate of the verified HCL site_url stack output (confirmed at L62-63). Verification ran out of turns on the duplicate.
[L336] content/templates/static-website/aws/index.md — "For typescript, python, go, csharp, yaml variants, the ACM certificate resource is added just above the aws.cloudfront.Distribution declaration." — Mis-sourced: This describes the page's own walkthrough text ("just above the aws.cloudfront.Distribution declaration, add these lines…"), which is present and correct in the diff. External verification wasn't the right check for the page's own tutorial content.
[L567] content/templates/static-website/aws/index.md — "In the HCL variant, the ACM certificate uses DNS as the validation method (validation_method = 'DNS')." — Mis-sourced: Confirmed by the page's own added HCL code, which sets validation_method = "DNS" on the aws_acm_certificate resource. External search couldn't confirm the page's own tutorial code.
[L592] content/templates/static-website/aws/index.md — "For typescript, python, go, csharp, yaml variants, the CloudFront configuration is extended by adding an aliases argument and adjusting viewerCertificate t…" — Mis-sourced: This is the page's own walkthrough text; the HCL twin of the same step (L598) verified. Self-consistent page content, not an external claim.
[L714] content/templates/static-website/aws/index.md — "A Route 53 A record is added to create a DNS record pointing to the CloudFront CDN." — Mis-sourced: The page's own walkthrough adds the Route 53 A record (the HCL aws_route53_record "domain" block with type = "A" is in the diff). Self-consistent page content.
[L904-906] content/templates/static-website/aws/index.md — "In the HCL variant, the stack output domain_url is exported with the value https://${local.domain_name}." — Mis-sourced: Confirmed by the page's own added HCL code: output "domain_url" { value = "https://${local.domain_name}" }. External search looked for what is the page's own tutorial code.

💡 Pre-existing issues in touched files (optional)

[L57-58] content/templates/static-website/gcp/index.md — "The cdnURL stack output is the fully-qualified HTTPS URL of the Google Cloud CDN (for TypeScript, Python, Go, C#, and YAML)." — Pre-existing: This cdnURL description sits on a line this PR didn't change, and verification found the GCP template programs export an http:// URL, not https://. Worth correcting — but note this PR mirrors the same "HTTPS" wording into the new HCL cdn_url block (L70-71), so if you fix it, fix both.
[L69-77] content/templates/serverless-application/aws/index.md — "For the TypeScript, Python, Go, C#, and YAML language variants of the AWS Serverless Application template, the configuration setting code specifies the path…" — Pre-existing: The non-HCL code configuration setting is documented on lines this PR only wrapped in a choosable block; verification found the AWS serverless templates hardcode the function archive and expose no code setting. A pre-existing inaccuracy, not introduced here.
[L117] content/templates/kubernetes/gcp/index.md — *"All configuration settings for the Kubernetes Cluster template are optional and may be adjusted by editing the stack configuration file directly (by default, …"* — **Pre-existing:** The "All of these settings are optional" line sits in tension with the pre-existing "You must supply an existing Google Cloud project ID" instruction (the config list includes gcp:project). Both lines predate this PR; the PR only wrapped them in choosable` blocks.

✅ Resolved since last review

No items resolved since the last review.

📜 Review history

2026-06-26T00:43:20Z — Reviewed HCL-variant additions across 18 template pages and the chooser/langfile wiring; no merge blockers — 6 contradictions triaged to pre-existing non-HCL text or verification artifacts, 3 pre-existing issues surfaced, and 2 low-confidence items flagged for author confirmation (8de46dc)

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.)

CamSoper

This looks great, @cnunciato!

cnunciato temporarily deployed to testing June 24, 2026 01:01 — with GitHub Actions Inactive

cnunciato requested review from CamSoper and jkodroff June 26, 2026 00:03

cnunciato mentioned this pull request Jun 26, 2026

Add HCL versions of all architecture and cloud starter templates pulumi/templates#1141

Open

cnunciato changed the title ~~Add HCL language option to architecture template pages~~ Add HCL templates to template pages Jun 26, 2026

cnunciato marked this pull request as ready for review June 26, 2026 00:38

cnunciato added the do-not-merge label Jun 26, 2026

cnunciato temporarily deployed to testing June 26, 2026 00:43 — with GitHub Actions Inactive

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 Jun 26, 2026

CamSoper approved these changes Jun 26, 2026

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Add HCL templates to template pages#19831

Add HCL templates to template pages#19831
cnunciato wants to merge 2 commits into
masterfrom
cnunciato/hcl-template-tabs

cnunciato commented Jun 24, 2026 •

edited

Loading

Uh oh!

pulumi-bot commented Jun 24, 2026 •

edited

Loading

Uh oh!

pulumi-bot commented Jun 24, 2026 •

edited

Loading

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

CamSoper left a comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Uh oh!

Conversation

cnunciato commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pulumi-bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

pulumi-bot commented Jun 24, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Lighthouse Performance Report

Uh oh!

github-actions Bot commented Jun 26, 2026

Pre-merge Review — Last updated 2026-06-26T00:43:20Z

🔍 Verification trail

Uh oh!

github-actions Bot commented Jun 26, 2026

Uh oh!

github-actions Bot commented Jun 26, 2026

🚨 Outstanding in this PR

⚠️ Low-confidence

📋 Triaged verifier findings

💡 Pre-existing issues in touched files (optional)

✅ Resolved since last review

📜 Review history

Uh oh!

CamSoper left a comment

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

cnunciato commented Jun 24, 2026 •

edited

Loading

pulumi-bot commented Jun 24, 2026 •

edited

Loading

pulumi-bot commented Jun 24, 2026 •

edited

Loading