Skip to content
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

[Workers] Custom access control for files in R2 using D1 and Workers #14618

Open
wants to merge 4 commits into
base: production
Choose a base branch
from

Conversation

justDMNK
Copy link

Hi everyone,

I just finished the tutorial called "Custom access control to images in R2 using D1 and Workers" which I proposed for the Developer Spotlight round. Just to address the possible confusion, I slightly adjusted the title to better reflect the content.

I tried to adhere and include the formatting guide as best as possible.
Please let me know if there is anything to be improved, thanks.

@github-actions github-actions bot added product:workers Related to Workers product size/m labels May 16, 2024
Copy link

gitguardian bot commented May 16, 2024

⚠️ 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 GitGuardian status Secret Commit Filename
- Generic High Entropy Secret a469395 content/workers/tutorials/custom-access-control-for-files-in-R2-using-D1-and-Workers 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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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


🦉 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.

@justDMNK justDMNK changed the title Developer Spotlight - Custom access control for files in R2 using D1 and Workers [Workers] Custom access control for files in R2 using D1 and Workers May 20, 2024
@megaconfidence
Copy link
Member

Hey @justDMNK thanks for working on this article. While it's in the middle of a technical review, can you fix the following?

  1. Move the content into an index.md file and place in a folder i.e custom-access-control-for-files-in-r2-using-d1-and-workers/ in the same directory?
  2. Fix the formatting of the content. This is what it looks like today
image

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants