camunda / github-backup Goto Github PK

If running time is 50+ minutes it should send timeout signal and printout all currently running (failed) jobs.

This would allow a more intuitive ordering by default.

As fas as I am concerned this change can be implemented in a breaking fashion, manual cleanup is not so hard.

Motivation: For Cawemo we currently manage our tasks and open problems via Github Issues and Milestones and it would be great to backup them alongside our code, maybe even more important than the code since nearly every developer has a local checkout of the code. (We don't use Github's Pull Requests for now.)

I care about both, open and closed issues (for different reasons) and their metadata like labels, assignees, milestones and comments. Some of our issues have attachments/embedded pictures (e.g. https://github.com/camunda/cawemo/issues/1123), they are not critical but would be a nice addon.

Persistence: Since this about backups only, in contrast to git repositories the restore of issues is way harder and does not need to be solved now. Facing that, some kind of barely human readable format (YAML > JSON) would be nice, having each issue in a separate file and the whole bunch then compressed afterwards and stored alongside in the S3 bucket. We have around 200 open and 1000 closed issues now. I have no preference for the directory structure, for file browsing experience it maybe should not be all in one directory.

One can touch it but it would be even nicer :)

Since Password authentication was outlawed by GitHub, using OAuth tokens seems to be the way to go.

The underlying GitHub client supports this, but github-backup lacks the high level configuration variables.

• add support for a GITHUB_TOKEN environment variable
• (optional) add support for a GITHUB_APP_KEY environment variable

Would be nice to be able to run it on Docker containers with Alpine.