cloudflare-docs
cloudflare-docs copied to clipboard
DS-12169 WAE public beta
TODO:
- [x] How to connect grafana.
- [ ] Some more info on setting up the binding / how to use the workers API?
- [ ] Particularly, writing of indexes is not mentioned anywhere.
- [x] Update details of FORMATs if we change that.
- [x] Include index1 in table schema section.
- [x] Update "Get Started" page to reflect the proper way of averaging with
_sample_interval. - [x] index page says we're in closed beta.
Deploying with
Cloudflare Pages
| Latest commit: |
649c676
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://6830658b.cloudflare-docs-7ou.pages.dev |
| Branch Preview URL: | https://jhawkridge-ds-12169-wae-publ.cloudflare-docs-7ou.pages.dev |
⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
| GitGuardian id | Secret | Commit | Filename | |
|---|---|---|---|---|
| 4092891 | Generic High Entropy Secret | 62b8ca9eee1e7fecef05bd45b3a18be008424443 | config.toml | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
Our GitHub checks need improvements? Share your feedbacks!
GitGuardian alert was caused by a commit from https://github.com/cloudflare/cloudflare-docs/pull/5879 that was accidentally merged into the PR. I force pushed to remove it but the alert remained.