4 ms·
> GitHub Next investigates the future of software development. Yesterday I tried to use Datadog's Github integration for stacktraces and it asked me for "acces
by vemv 4y ago
> GitHub Next investigates the future of software development.
Yesterday I tried to use Datadog's Github integration for stacktraces and it asked me for "access Github on my behalf".
It's been the same since the beginning of Github - they leave integrators with no better options, and users with an ambiguous UI dialog / docs that downplay the scope being granted.
Sooooo maybe fix your own stuff before making such grandiose claims?
- saurik 4y agoWhy wouldn't this be done over git? It seems almost ridiculous for this to be a GitHub-specific API and authentication mechanism instead of merely authorizing an SSH key from Datadog (which would then allow whatever this service is doing with the source code to also work for any other source code hosting solution).
- hobofan 4y agoBecause DataDog's GitHub integration does in addition to git data also take GitHub data into account to provide a better user experience. E.g. for giving "this action broke this thing" insights giving you a clickable link to a GitHub PR instead of just providing you with a git SHA hash. They also provide a direct git integration, which as far as I can tell just is a reduced version of the GitHub one, with a featureset that seems reasonable if they only have the pure git data.
- bastardoperator 4y agoMetadata lives in the API, not the git repo. I would argue a github app with rotating hourly tokens which datadog seems to support is better than a users ssh key or an ssh key with access to many repos.