Remove "Crosswalk" branding in favor of "awsx" - #2988
Merged
Conversation
cnunciato
approved these changes
Aug 27, 2026
cnunciato
left a comment
cnunciato
left a comment
Contributor
There was a problem hiding this comment.
Few lil' things to fix up, but otherwise 👍🏻 !
| options: | ||
| virtualenv: venv | ||
| description: Fargate with crosswalk vpc | ||
| description: Fargate with awsx vpc |
Contributor
There was a problem hiding this comment.
Suggested change
| description: Fargate with awsx vpc | |
| description: Fargate with AWSx vpc |
I'll stop commenting on these and leave the rest to search & replace. 😄
| ### What Is This? | ||
|
|
||
| This example uses [Pulumi CrossWalk for AWS](https://www.pulumi.com/docs/guides/crosswalk/aws/#pulumi-crosswalk-for-aws) for deploying your own vpc using crosswalk [VPC](https://www.pulumi.com/docs/guides/crosswalk/aws/vpc/). The VPC is built in `typescript` | ||
| This example uses the Pulumi [awsx](https://www.pulumi.com/docs/iac/guides/clouds/aws/) package for deploying your own vpc using the awsx [VPC](https://www.pulumi.com/docs/iac/guides/clouds/aws/vpc/) component. The VPC is built in `typescript` |
Contributor
There was a problem hiding this comment.
Suggested change
| This example uses the Pulumi [awsx](https://www.pulumi.com/docs/iac/guides/clouds/aws/) package for deploying your own vpc using the awsx [VPC](https://www.pulumi.com/docs/iac/guides/clouds/aws/vpc/) component. The VPC is built in `typescript` | |
| This example uses the Pulumi [AWXx](https://www.pulumi.com/docs/iac/guides/clouds/aws/) package for deploying your own VPC using the AWSx [VPC](https://www.pulumi.com/docs/iac/guides/clouds/aws/vpc/) component. The VPC is written in TypeScript. |
We no longer refer to any library as "Crosswalk". Every reference to the term is replaced with the name of the package these examples actually consume: "AWSx" in prose, "awsx" where it's an identifier. Most of it lived in aws-ts-vpc-with-ecs-fargate-py, where the term was baked into names as well as prose: - Renamed vpc-crosswalk-ts/ to vpc-awsx-ts/ - Renamed the Pulumi projects crosswalk-vpc -> awsx-vpc and fargate-with-crosswalk-vpc -> fargate-with-awsx-vpc - Renamed the "crosswalk"/"crosswalk-vpc" resource tags to "awsx"/"awsx-vpc" - Updated the pasted `pulumi up` and `pulumi stack output` transcripts in the READMEs so the samples match what the renamed projects now print Also fixed two mentions elsewhere: the "using AWS Crosswalk" comment in aws-go-fargate (which does import pulumi-awsx), and a stale doc URL in aws-ts-apigateway-lambda-serverless. The /docs/guides/crosswalk/aws/... URLs were stale as well as off-brand; they now point at /docs/iac/guides/clouds/aws/..., which is where they redirect to. While in ecs-fargate-python/README.md, corrected two relative links that resolved against ecs-fargate-python/ and pointed at nothing. This has to happen here because pulumi/registry generates its aws-ts-vpc-with-ecs-fargate-py how-to-guide from these READMEs via mktutorial, and that file is marked do-not-edit. Note: renaming the directory breaks the old ?template= deploy-button URL, and the project rename changes the StackReference path for anyone with a stack deployed from the old names. Fixes #2987 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KiBQ3FUHakhvydtYErXfXi
jkodroff
force-pushed
the
jkodroff/remove-crosswalk
branch
from
August 28, 2026 14:02
3d2cd18 to
4b3d3d9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #2987. Part of pulumi/registry#10607 — we no longer refer to any library as "Crosswalk", so every reference to the term is replaced with awsx, the name of the package these examples actually consume.
Most of it lived in
aws-ts-vpc-with-ecs-fargate-py, where the term was baked into names as well as prose. This does the full rename (the "Part 2" the issue flagged as needing a decision):vpc-crosswalk-ts/vpc-awsx-ts/crosswalk-vpcawsx-vpcfargate-with-crosswalk-vpcfargate-with-awsx-vpc"crosswalk": "yes""awsx": "yes""crosswalk-vpc": "yes""awsx-vpc": "yes"/docs/guides/crosswalk/aws/…/docs/iac/guides/clouds/aws/…The pasted
pulumi up/pulumi stack outputtranscripts in the READMEs are updated too, so the samples match what the renamed projects now actually print.Also fixed two mentions outside the issue's stated scope, both one-liners:
aws-go-fargate/main.go— "using AWS Crosswalk" comment (it does importpulumi-awsx)aws-ts-apigateway-lambda-serverless/index.ts— stale crosswalk doc URLThe old
/docs/guides/crosswalk/aws/…URLs were stale as well as off-brand; the new ones are where they already redirect to (verified: new 200, old 301).Drive-by fix:
ecs-fargate-python/README.mdlinked to./vpc-crosswalk-tsand./ecs-fargate-python, both of which resolve againstecs-fargate-python/and pointed at nothing. Corrected to../.Why it has to happen here
pulumi/registrygeneratesthemes/default/content/registry/packages/aws/how-to-guides/aws-ts-vpc-with-ecs-fargate-py.mdfrom these READMEs viamktutorial, and that file is marked "generated by a tool — do not edit". The published page only stops saying "Crosswalk" once these sources change.?template=deploy-button URL for the oldvpc-crosswalk-ts/README.mdpath will 404. Anyone linking to it externally will need to update.StackReferencepath (<org>/crosswalk-vpc/<stack>→<org>/awsx-vpc/<stack>) for anyone with a stack already deployed from this example.Verification
grep -rin crosswalkacross the repo returns nothing.black --checkpasses on the changed Python file.tsconfig.jsonusesfiles: ["index.ts"]and a relativeoutDir), and nothing inmisc/test/,Makefile,scripts/, or.github/referenced the old path — there is no integration test for this example, so there's nothing in the test matrix to update.go buildandeslintcouldn't run (full disk / ESLint deps not installed locally), so CI is the real check on those. Both edits there are a single comment/string line.🤖 Generated with Claude Code
https://claude.ai/code/session_01KiBQ3FUHakhvydtYErXfXi