Skip to content

Conversation

@CamSoper
Copy link
Contributor

@CamSoper CamSoper commented Nov 19, 2025

This is a significant update to the Get Started experience for Azure, Google Cloud, and Kubernetes users.

  • Each of these three Get Started tutorials has been rewritten to mirror the AWS version as closely as possible, with some constraints based on the specific project template.

  • The AWS Get Started got some formatting consistency updates and minor language adjustments.

  • The Get Started experience was tested end-to-end for each cloud both manually and with AI assistance.

Apologies for the large PR! In retrospect, I should have broken this into 3.

Fixes #16104

…nhance deploy stack and destroy stack sections, and streamline project review content. Update GCP and Kubernetes guides to focus on installation steps. Introduce a new shortcode for installation instructions.
@CamSoper CamSoper changed the title Refactor and update installation guides for Azure, GCP, and Kubernetes Refactor and update get started guides for Azure, GCP, and Kubernetes Nov 19, 2025
@claude

This comment was marked as outdated.

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@CamSoper CamSoper marked this pull request as ready for review December 5, 2025 23:31
@claude
Copy link
Contributor

claude bot commented Dec 5, 2025

Documentation Review

I have reviewed the changes to refactor and update the Get Started guides for Azure, GCP, and Kubernetes to follow the same structure as AWS. Here are my findings:

Overall Assessment

This is a comprehensive refactoring that successfully aligns the Azure, GCP, and Kubernetes Get Started guides with the AWS guide structure. The changes improve consistency and user experience across all cloud providers.

Issues Found

1. Missing aliases verification (SEO Critical)

The following files were deleted without obvious replacements:

  • content/docs/iac/get-started/azure/deploy-changes.md
  • content/docs/iac/get-started/azure/review-project.md
  • content/docs/iac/get-started/gcp/deploy-changes.md
  • content/docs/iac/get-started/gcp/review-project.md
  • content/docs/iac/get-started/kubernetes/deploy-changes.md
  • content/docs/iac/get-started/kubernetes/review-project.md

Per AGENTS.md, you must:

  1. Add aliases to the frontmatter of replacement pages (if content was merged into other pages)
  2. Add S3 redirects in /scripts/redirects/ if these were standalone pages
  3. Use the alias verification scripts in /scripts/alias-verification/ to verify all moved files have proper aliases

2. C# code formatting inconsistency

In content/docs/iac/get-started/aws/create-component.md:555, consider using Array.Empty for better C# idiomaticity.

3. Unnecessary explicit namespace

In content/docs/iac/get-started/aws/create-component.md:756 and content/docs/iac/get-started/aws/create-project.md:299, the change from Deployment.RunAsync() to Pulumi.Deployment.RunAsync() is inconsistent with the using Pulumi statement. Either remove the explicit namespace or remove the using statement for consistency.

4. Frontmatter identifier inconsistency

Some files have the identifier field in frontmatter (e.g., azure-get-started.configure), but others do not. Review whether identifiers should be added consistently across all similar pages.

Positive Changes

  • Excellent consistency improvements across all cloud provider guides
  • Addition of dedicated Configure sections for each provider
  • New Create component sections that teach infrastructure abstractions
  • Improved link formatting with proper quote marks
  • Better structure matching the AWS guide
  • Good use of shortcodes for reusable content

Next Steps

  1. Verify and add aliases/redirects for deleted files (SEO critical)
  2. Run the alias verification scripts
  3. Review the minor consistency issues noted above

@claude Mention me if you would like help addressing any of these issues or if you need additional reviews after making changes.

@CamSoper
Copy link
Contributor Author

CamSoper commented Dec 5, 2025

@claude -

  1. Please add those aliases to the Overview page of each respective tutorial.
  2. Ignore, that was deliberate.
  3. Ignore, that was deliberate because it resolves an ambiguous namespace
  4. Check each file and add the missing identifiers

Thank you! Here's a cookie. 🍪

@claude
Copy link
Contributor

claude bot commented Dec 5, 2025

Claude finished @CamSoper's task —— View job


Completed your request! ✓

Thanks for the cookie! 🍪 Here's what I did:

Tasks

  • Add aliases to Azure _index.md for deleted files
  • Add aliases to GCP _index.md for deleted files
  • Add aliases to Kubernetes _index.md for deleted files
  • Identify files with missing frontmatter identifiers
  • Add missing identifiers to frontmatter
  • Commit and push changes

Summary

1. Aliases added
I've successfully added aliases to the overview pages (_index.md) for all three cloud providers:

  • Azure: Added aliases for /docs/iac/get-started/azure/deploy-changes/ and /docs/iac/get-started/azure/review-project/
  • GCP: Added aliases for /docs/iac/get-started/gcp/deploy-changes/ and /docs/iac/get-started/gcp/review-project/
  • Kubernetes: Added aliases for /docs/iac/get-started/kubernetes/deploy-changes/ and /docs/iac/get-started/kubernetes/review-project/

2. C# code formatting (ignored per your request)

3. Namespace qualification (ignored per your request)

4. Frontmatter identifiers
I verified all files across Azure, GCP, and Kubernetes Get Started guides. Good news: all files already have the required identifier field in their frontmatter! No changes were needed for this task.

All changes have been committed and pushed to your branch CamSoper/issue16104.

--- |

Added aliases to Azure, GCP, and Kubernetes overview pages for the deleted deploy-changes and review-project files to maintain SEO and prevent broken links.

Co-authored-by: Cam Soper <CamSoper@users.noreply.github.com>
@pulumi-bot
Copy link
Collaborator

@CamSoper CamSoper requested review from jkodroff and joeduffy December 6, 2025 00:16

{{% /choosable %}}

Before you begin, watch this overview of how to deploy Kubernetes infrastructure with Pulumi:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Huh, I didn't realize we have this. Isn't it possible this will lead to dropoff? The NEXT button is below the big video and it sort of makes it seem like I need to watch a 10 minute video before proceeding. I like the idea of having content like this but maybe it should go on the final "next steps" page?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had assumed that somebody stuck it there on purpose. I like the idea of moving it to the next steps, I'll do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bring improved Get Started flow to other clouds

4 participants