Updated cody analytics cookie name to SAMS cookie #1284
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
|
||
| For Sourcegraph Analytics, you can generate an access token for programmatic access. Tokens are long-lived with an optional expiry and have the same permissions to access instance data as the user who created them. | ||
|
|
||
| ### Getting Started |
There was a problem hiding this comment.
Is it worth adding an info callout block saying that on N date, the cookie used got changed?
There was a problem hiding this comment.
Good point. Added note!
| - Retrieve your session cookie, `cas`, from your browser's developer tools. | ||
| - Retrieve your SAMS session cookie, `accounts_session_v2`, from your browser's developer tools. | ||
|
|
||
|  |
There was a problem hiding this comment.
Note: I will update this image when https://github.com/sourcegraph/cody-analytics/pull/207 is merged, and we use accounts_session_v2 in production (so it says analyitcs.sourcegraph.com as the cookie source instead of localhost)
Co-authored-by: Robert Lin <[email protected]>
|
SAMS is an internal term, for external communication we consistently use “Sourcegraph Accounts” and no need to mention SAMS. |
Got it, updated! |
Co-authored-by: James Cotter <[email protected]>
Co-authored-by: James Cotter <[email protected]>
This reverts commit aaf80f2.
Reverts #1284 Temporary until we figure out SAT enablement: https://sourcegraph.slack.com/archives/C06358CMSRM/p1753978693642839?thread_ts=1753973156.343589&cid=C06358CMSRM
4 participants
Updated documentation on how to use Sourcegraph Analytics API. Once PR-207 is merged, the
cascookie will be updated toaccounts_session_v2, unifying SAMS user sessions and closing CORE-850This PR will only be merged once PR-207 is fully tested and merged.