HCP Boundary Product Migration#1902
HCP Boundary Product Migration#1902rmainwork wants to merge 2 commits intorm/hcp-docs-relocationfrom
Conversation
Vercel Previews Deployed
|
05c75c5 to
a143690
Compare
Broken Link CheckerThis PR contains broken links, but won't be blocked. Use this report to improve content quality: Quick Actions
Need Help?
Internal LinksExternal LinksSummary
Redirects per inputRedirects in content/hcp-boundary/docs/hcp-docs/audit-logging.mdx
Redirects in content/hcp-boundary/docs/hcp-docs/self-managed-workers/size-self-managed-workers.mdx
|
|
Hey @Dan-Heath! So, it's not dependent on #1856 for preview, just for merge (because of the way that PRs are stacked and I understand that global partials are a pre-requisite the HCP docs migration to land). It is however dependent on hashicorp/dev-portal#2966 for preview (and vice versa, which is why the Vercel build on that one is failing). If you wanted to preview it, you could |
8fb909f to
e38c6e0
Compare
e38c6e0 to
59d702b
Compare
Thank you @rmainwork ! That makes sense 👍 |
a143690 to
9a6eb5b
Compare
|
Just an FYI folks - now that global partials has landed, I've rebased this onto |
As-per the RFC, HCP product docs will be extracted from `hcp-docs` up to their own top level product folder
Update pr labeller to label changes to /content/hcp-boundary as "HCP Boundary" and the CODEOWNERS file to point to match the existing self-hosted Boundary rules and remove the old hcp-docs/boundary rule(s)
8ad4a9a to
f95cdd4
Compare
|
FYI: have rebased this PR/branch onto an integration branch to keep all the HCP work together. |
Migrates content from
/content/hcp-docs/boundaryto/content/hcp-boundaryand updatesproductConfigto configure it as a top level product.There is a sister PR here to configure devdot to source content correctly.