You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Cloud Logs is not connected to its remote API yet. Implement the API calls in electron-app/src/cloudLogs/client.js to list logs, suggest tags, upload session ZIPs with their user, date, notes, and tags, and download ZIPs by ID.
Follow the API contract in electron-app/src/cloudLogs/README.md. Show clear errors when requests fail, and never expose the API key to the renderer.
Files to modify:
electron-app/src/cloudLogs/client.js — implement the API calls.
electron-app/src/cloudLogs/README.md — document the real endpoints, authentication, and response formats.
frontend/frontend-kit/kit/src/core/cloudLogs.ts — shared request and response types.
electron-app/src/cloudLogs/handlers.js — how the client is called and errors are passed to the UI.
electron-app/src/cloudLogs/archive.js — ZIP creation and extraction.
electron-app/src/cloudLogs/tests/storage.test.js — local archive and credential tests.
.github/workflows/electron-tests.yaml — runs the Electron tests.
How to work with control station
Firstly, download the repo and ALL (including go) its requirements, read README.md
Then use pnpm install to install all the dependencies (including python dependencies)
As you'll be working with an Electron app, I recommend building the full Control Station application throughout development. There is a dev mode, but it's not as reliable as the full build. Apart from the initial build, subsequent builds don't take too long, so I think it's worth sticking with the full build.
Build the app with pnpm run build and open the app with pnpm start
Remember all commands are runned at the root of the repo.
Before starting development create the PR as a draft to logging view enhancement branch, (not to develop).
Activity
chore: start cloud logs integration (#677)