Skip to content

Migrate WAF to UDR #450

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 139 commits into from
Aug 11, 2025
Merged

Migrate WAF to UDR #450

merged 139 commits into from
Aug 11, 2025

Conversation

im2nguyen
Copy link
Collaborator

@im2nguyen im2nguyen commented May 29, 2025

This is an experimental branch to migrate WAF (Well Architected Framework) content into UDR. In addition, it converts the WAF content layout from "tutorials" to "docs", a long-standing request by CJ.

This requires changes to the dev-portal repo too.

🔍 Preview

@im2nguyen im2nguyen requested a review from a team as a code owner May 29, 2025 08:06
@im2nguyen im2nguyen requested a review from LeahMarieBush May 29, 2025 08:06
Copy link

github-actions bot commented May 29, 2025

Vercel Previews Deployed

Name Status Preview Updated (UTC)
Dev Portal ✅ Ready (Inspect) Visit Preview Thu Aug 7 20:24:45 UTC 2025
Unified Docs API ✅ Ready (Inspect) Visit Preview Thu Aug 7 20:14:18 UTC 2025

@@ -3,7 +3,7 @@

services:
dev-portal:
image: 'hashicorp/dev-portal:latest'
image: 'dev-portal:waf-docs'
Copy link
Contributor

Choose a reason for hiding this comment

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

@im2nguyen what is the difference between these two images of dev-portal?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

It's updating it from tutorials to docs: hashicorp/dev-portal#2763

Copy link
Contributor

@judithpatudith judithpatudith left a comment

Choose a reason for hiding this comment

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

I think this goes through the end of automate! Submitting it now so you have it Monday!


# Define your infrastructure systems

Before you can automate your infrastructure processes, you need to clearly define what infrastructure systems and tools you need. Using infrastructure as code (IaC) to define your systems creates a clear, version-controlled specification of your infrastructure that can be reviewed, tested, and automated.
Copy link
Contributor

Choose a reason for hiding this comment

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

I'm not sure this paragraph makes any sense. IaC is how you codify your infrastructure, but here we're saying that before we codify it we should define it, and we should define it by codifying it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

"automate your infrastructure" -> using hcp terraform <> gitops to deploy your terraform config when you change it (fully automated workflow)

"defining your infrastructure" -> taking what you have and turning into terraform (semi-automated workflow)

cjobermaier and others added 13 commits August 4, 2025 09:27
…te-processes/process-automation/index.mdx

Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
…te-processes/process-automation/fully-automated.mdx
…te-processes/define/workflows.mdx

Co-authored-by: Judith Malnick <judith@hashicorp.com>
…te-processes/define/as-code/monitoring.mdx

Co-authored-by: Judith Malnick <judith@hashicorp.com>
…te-processes/define/as-code/database.mdx

Co-authored-by: Judith Malnick <judith@hashicorp.com>
Co-authored-by: Judith Malnick <judith@hashicorp.com>
@roooms
Copy link

roooms commented Aug 6, 2025

I've had a read through of the structure and hierarchy of this content but haven't had the time to read every one of the 99 mdx files included in this change. Overall I think the section and page headings are great and a much better approach than following other examples of a WAF. This feels much more HashiCorp.

Couple of points that need addressing:

  • I found quite a few broken links when topics link to further reading. I think most of these were when jumping between WAF and docs, so maybe that will resolve itself once everything merges, but it should be checked.
  • I don't think the implementation resources section fits in the WAF and could be a good breakpoint to provide more guidance to Ent customers in an agreed format.
  • I still find it awkward that we're addressing both CE and Ent in the same space and providing scale guidance for CE. Is the goal of this content to make readers successful at scale with our CE tools? Is there any expectation or recommendation that they need to move to Ent to scale? Our CE tools are one of the biggest competitors for successful commercial customer acquisition.

@cjobermaier
Copy link
Contributor

Before merge we need to remove the sleep from the GHA

cjobermaier and others added 2 commits August 6, 2025 11:43
Add sleep so dev-portal finishes after dev portal preview. This makes sure the new WAF preview builds.
Copy link

github-actions bot commented Aug 6, 2025

Broken Link Checker

Summary

Status Count
🔍 Total 871
✅ Successful 849
⏳ Timeouts 0
🔀 Redirected 0
👻 Excluded 21
❓ Unknown 0
🚫 Errors 1

Errors per input

Errors in content/well-architected-framework/docs/docs/secure-systems/validate-software-integrity.mdx

command: |
cd unified-docs-frontend-preview
sleep 300
Copy link
Contributor

Choose a reason for hiding this comment

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

Remove before merge.

@cjobermaier cjobermaier merged commit 8d0a4dd into main Aug 11, 2025
14 of 16 checks passed
@cjobermaier cjobermaier deleted the migrate-waf-to-udr branch August 11, 2025 16:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants