[D1] D1 HTTP API tutorial

[harshil1712]

Updated #15779

[cloudflare-workers-and-pages]

Deploying cloudflare-docs with    Cloudflare Pages

Latest commit:	9ceecaf
Status:	✅  Deploy successful!
Preview URL:	https://14658654.cloudflare-docs-7ou.pages.dev
Branch Preview URL:	https://d1-http-tutorial-new.cloudflare-docs-7ou.pages.dev

View logs

[github-actions]

Files with changes (up to 15)

Original Link	Updated Link
https://developers.cloudflare.com/d1/tutorials/build-an-api-to-access-d1/	https://d1-http-tutorial-new.cloudflare-docs-7ou.pages.dev/d1/tutorials/build-an-api-to-access-d1/

[hyperlint-ai]

1 files reviewed, 1 outstanding issue(s) found.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11021221	Triggered	Generic High Entropy Secret	81195ad	astro.config.mjs	View secret
11021221	Triggered	Generic High Entropy Secret	81195ad	astro.config.mjs	View secret
11021221	Triggered	Generic High Entropy Secret	81195ad	astro.config.mjs	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[hyperlint-ai]

1 files reviewed, 1 outstanding issue(s) found.

[hyperlint-ai]

1 files reviewed, 18 outstanding issue(s) found.

[harshil1712]

@Oxyjun left a few comments. Just some minor suggestion :D

[bllchmbrs]

@Oxyjun and @dbenCF , hyperlint developer here. I was just looking over this pull request - seems like. a lot of false comments from Hyperlint.

It looks as if the problem was the indentation triggering a lot of false positives. Anything else that you think I'm missing here?

cc @kodster28 for visibility.

We're actively improving the model based on this information, so I want to make sure that we get it right!

One of my questions is, are indentations like this common / going to be more common?