-
Notifications
You must be signed in to change notification settings - Fork 47
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
Migrate WAF to UDR #450
Conversation
Vercel Previews Deployed
|
docker-compose.yaml
Outdated
@@ -3,7 +3,7 @@ | |||
|
|||
services: | |||
dev-portal: | |||
image: 'hashicorp/dev-portal:latest' | |||
image: 'dev-portal:waf-docs' |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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
…ne-processes/create-high-performing-teams/collaboration.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
…ne-processes/create-high-performing-teams/collaboration.mdx Co-authored-by: Tu Nguyen <im2nguyen@users.noreply.github.com>
Merge create high performing teams into WAF branch https://hashicorp.atlassian.net/jira/software/c/projects/WAF/boards/2173?assignee=63690774d60bd2b365f85ffa&assignee=627a65e0f29dcb0068f86381&selectedIssue=WAF-316
There was a problem hiding this 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!
...ocs/define-and-automate-processes/build-culture/create-high-performing-teams/recognition.mdx
Show resolved
Hide resolved
content/well-architected-framework/docs/docs/define-and-automate-processes/define/workflows.mdx
Outdated
Show resolved
Hide resolved
|
||
# 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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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)
...hitected-framework/docs/docs/define-and-automate-processes/define/as-code/infrastructure.mdx
Outdated
Show resolved
Hide resolved
...ll-architected-framework/docs/docs/define-and-automate-processes/define/as-code/database.mdx
Outdated
Show resolved
Hide resolved
...ll-architected-framework/docs/docs/define-and-automate-processes/define/as-code/database.mdx
Outdated
Show resolved
Hide resolved
...ll-architected-framework/docs/docs/define-and-automate-processes/define/as-code/security.mdx
Show resolved
Hide resolved
...-architected-framework/docs/docs/define-and-automate-processes/define/as-code/monitoring.mdx
Outdated
Show resolved
Hide resolved
...-architected-framework/docs/docs/define-and-automate-processes/define/as-code/monitoring.mdx
Show resolved
Hide resolved
...ted-framework/docs/docs/define-and-automate-processes/process-automation/fully-automated.mdx
Outdated
Show resolved
Hide resolved
…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>
…-docs into migrate-waf-to-udr
Co-authored-by: Judith Malnick <judith@hashicorp.com>
…-docs into migrate-waf-to-udr
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:
|
Before merge we need to remove the |
Add sleep so dev-portal finishes after dev portal preview. This makes sure the new WAF preview builds.
Broken Link CheckerSummary
Errors per inputErrors in content/well-architected-framework/docs/docs/secure-systems/validate-software-integrity.mdx
|
command: | | ||
cd unified-docs-frontend-preview | ||
sleep 300 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Remove before merge.
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