build: cdi manual

[crazy-max]

Description

Adds CDI page to build section.

Related issues or tickets

• Error when using RUN --device buildx#3295
• Support RUN --gpus ... or equivalent. moby/buildkit#1436
• CDI support moby/buildkit#4056

Reviews

• Technical review
• Editorial review
• Product review

[netlify]

✅ Deploy Preview for docsdocker ready!

Name	Link
🔨 Latest commit	3153d21
🔍 Latest deploy log	https://app.netlify.com/projects/docsdocker/deploys/6871372fd7996a0008796f0a
😎 Deploy Preview	https://deploy-preview-23069--docsdocker.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[ArthurFlag]

Could you edit this line to

SECRETS_SCAN_OMIT_PATHS = "public/contribute/file-conventions/index.html,public/content/manuals/build/building/cdi.html"

?

[crazy-max]

Thanks looks good now but do you know why it is happening? Looking at the logs: https://app.netlify.com/projects/docsdocker/deploys/6870f8f33387050008ca7b11

1:45:06 PM: ❯ Scanning complete. 8540 file(s) scanned. Secrets scanning found 0 instance(s) of secrets and 1 instance(s) of likely secrets in build output or repo code.
1:45:06 PM: ​
1:45:06 PM: "LS0t***" detected as a likely secret:
1:45:06 PM:   found value at line 719 in public/build/building/cdi/index.html
1:45:06 PM: ​
1:45:06 PM: To prevent exposing secrets, the build will fail until these likely secret values are not found in build output or repo files.
1:45:06 PM: ​
1:45:06 PM: If these are expected, use SECRETS_SCAN_SMART_DETECTION_OMIT_VALUES, or SECRETS_SCAN_SMART_DETECTION_ENABLED to prevent detecting.
1:45:06 PM: ​
1:45:06 PM: For more information on secrets scanning, see the Netlify Docs: https://ntl.fyi/configure-secrets-scanning
1:45:06 PM: ​
1:45:06 PM: Secrets scanning detected secrets in files during build.      
1:45:06 PM: ────────────────────────────────────────────────────────────────

It says cdi page contains LS0t*** as secret but I don't have any occurrence like this.

[ArthurFlag]

The LST0 issue is the one we had a few weeks ago: it comes from codeblocks that we convert into Base64 for the copy button, so one of your codeblocks contains that string once converted 🙃

[crazy-max]

The LST0 issue is the one we had a few weeks ago: it comes from codeblocks that we convert into Base64 for the copy button, so one of your codeblocks contains that string once converted 🙃

Ah I see but still wonder why just file-conventions and cdi pages are affected and not others using codeblocks?

[thaJeztah]

Ah I see but still wonder why just file-conventions and cdi pages are affected and not others using codeblocks?

I guess just "luck" if the script base64 encodes the content of the codeblock (before styling).

[thaJeztah]

Did a quick check; LS0t is --- (base64 encoded)

[thaJeztah]

So; this probably is the cause 😆

[crazy-max]

Ah yes indeed looks related to

docs/layouts/_default/_markup/render-codeblock.html

Line 25 in 4ab3804

x-data="{ code: '{{ encoding.Base64Encode .Inner }}', copying: false }"

that was introduced in #18545