CloudAEye for 
Google Drive
Your team already wrote it down. Now new developers can find it.
Your design docs, runbooks, and setup guides already explain how things work. CodeCortex reads them alongside your code, so new developers get answers instead of a reading list.
Read-only Google Drive access You choose the folders
Google Drive · example onboarding question
Refund processing
Refunds are never issued inside the API request.
The API records the refund and returns 202. The refund worker calls the payment provider and retries for up to 24 hours.
Partial refunds can't exceed the captured amount.
Indexed from a folder you selected.
New
developerHow are refunds processed? I need to change the retry
window.
The API only records the request.
RefundWorker.process() calls the provider and
retries for up to 24 hours, set by
REFUND_RETRY_WINDOW in
refunds/settings.py.
| Service | Owner | On-call |
|---|---|---|
| payments-api | Payments team | #payments-oncall |
| ledger | Ledger team | #ledger-oncall |
| refunds-worker | Payments team | #payments-oncall |
| notifications | Platform team | #platform-oncall |
Indexed from a folder you selected.
New
developerWho should review my change to the ledger?
The ownership sheet lists the Ledger team for
services/ledger, on call in #ledger-oncall. Your
change touches LedgerEntry.post(), which the refund
worker also calls.
Indexed from a folder you selected.
New
developerWhy does the webhook handler keep a list of event IDs?
After an outage, the provider redelivered webhooks and each one
posted to the ledger again.
WebhookHandler.handle() now records event IDs in
processed_events and skips repeats for 72 hours.
Accurate answer from the team's knowledge.
OneDrive
YouTubeConnect once.
Every new hire benefits.
Set it up once in the CloudAEye console. After that, new developers just ask.
-
Week one:
get oriented.Learn the services, the setup, and the architecture from the docs your team already wrote, without waiting for someone to walk you through it.
First-week questions -
First change:
know the why.Before touching unfamiliar code, find the design doc, incident review, or runbook that shaped it.
First-change questions -
Every hire after:
answer once.Point new teammates to CodeCortex. The explanation you wrote once keeps answering.
Ongoing questions
You choose
what gets indexed.
Select folders and files. Everything else in your Drive stays out of CodeCortex.
29 files in 3 folders will be indexed.
CodeCortex indexes
- Google Docs, Sheets, and Slides
- PDF and Word (.docx)
- Markdown, reStructuredText, plain text, and logs
- CSV, JSON, YAML, and XML
Questions new developers
would otherwise ask you.
The questions that usually go to whoever has been here longest, answered from the docs your team already keeps.
Find the design behind a serviceFirst week
Locate the design doc that explains how a service works and why, then see where that design lives in the code.
How are refunds processed?
Which doc describes the ledger model?
Set up a local environmentFirst week
Follow the team's setup guide with the commands and config files it refers to, mapped to the repository.
How do I run payments-service locally?
Which environment variables do I need?
Understand why the code is the way it isFirst change
Connect a puzzling piece of code to the incident review or design decision that shaped it.
Why does the webhook handler keep event IDs?
Find the right reviewerFirst change
Look up ownership and on-call details from the sheets your team maintains, next to the code your change touches.
Who owns the ledger service?
Read the runbook before you touch production pathsFirst change
See the operational steps and known failure modes for the area you're about to change.
How do we roll back refunds-worker?
Stop answering the same question twiceOngoing
Link the question to the doc instead of retyping the answer. Every later hire gets the same explanation.
Where's the architecture overview?
Which doc covers our deployment process?
Your next new hire.
A faster first week.
Onboard developers in days, not months. Create a CloudAEye account, connect Google Drive, and choose the folders a new developer should learn from.
Connect Google Drive Talk to our team-
1
Sign in to CloudAEye
Create an account or sign in to the CloudAEye console.
-
2
Connect Google Drive
Sign in with Google and approve Drive's read-only consent screen.
-
3
Choose folders, then ask
Select the folders and files to index. When indexing finishes, ask it the questions a new developer would.
A few things worth knowing.
What access does CloudAEye request?
Google's read-only Drive permission (drive.readonly).
CloudAEye can read files, but can't edit, delete, or share them.
Is my whole Drive indexed?
No. Only the folders and files you select are indexed. Choose your engineering docs and leave everything else out.
Which files get indexed?
Google Docs, Sheets, and Slides; PDF and Word (.docx); Markdown, reStructuredText, plain text, and logs; CSV, JSON, YAML, and XML. Sheets are read as CSV, first tab only.
Does connecting Google Drive also ask for YouTube?
No. Google Drive and YouTube are connected separately, and each asks only for its own permissions.
Can I remove a file after it's indexed?
Yes. Remove an indexed file and CloudAEye deletes its indexed copy. Files are removed one at a time, not by folder.
What happens if I disconnect Google Drive?
CloudAEye deletes the stored connection and everything it indexed from your Drive.