3ea2070cdb
pass filename (it is not part of the config!)
2016-03-31 09:53:56 -07:00
9e7ae1a4f7
we really need a better linter
2016-03-31 09:38:40 -07:00
d27159275b
pick region as well
2016-03-31 09:34:57 -07:00
6c2ae756f1
fix usage of backupInfo
2016-03-31 09:23:41 -07:00
39cc5d07d1
use the backupdb config to determine bucket and prefix
2016-03-31 00:50:56 -07:00
df39384056
do not save backup secrets in database
2016-03-30 23:39:48 -07:00
c097651a88
store backup configuration as part of backups table
2016-03-30 15:04:39 -07:00
e2b7ec3ffd
store filename with tar.gz extension
2016-03-08 16:47:53 -08:00
d157bf30f3
remove box backups from the database
2016-03-08 08:52:20 -08:00
7996b32022
add backups to the database
...
ideally, these should be done _after_ the backup is successful and not when
the backup url is generated.
we had a discussion on why need backupdb to start with. Some rationale includes:
1. we can use it as a FK constraint (like make sure you delete backups when you delete app)
2. have labels for backups
3. dependancy relation from box backup to apps
4. s3 reverse sort is little painful and requires us to get all items in bulk and sort in JS
(also requires us to change our backup filename format)
5. any metadata storage requires database
The cons include:
1. s3 and this db go out of sync
2. db entry is useless if s3 file is missing
2016-03-08 08:42:00 -08:00
4dd82d10ad
backup: ensure same timestamp for app data and config
2016-03-07 12:13:54 -08:00
ea4862d351
Strictly assert on app
2016-01-29 11:54:40 +01:00
3e4d62329e
Also copy the backup config json
2016-01-29 11:54:15 +01:00
7b1d906494
Add backups.getAppBackupConfigUrl()
2016-01-29 11:44:24 +01:00
030faaa5d1
Remove unused information within backup listing
2015-12-30 20:31:00 +01:00
a5ef9ff372
Add getAllPaged to storage api
2015-11-08 22:41:13 -08:00
8df7f17186
load backup config from settingsdb
2015-11-07 22:06:09 -08:00
12200f2e0d
split aws code into storage backends
2015-11-06 18:22:29 -08:00
a853afc407
backups: add api call
2015-11-06 18:14:59 -08:00
de471b0012
return BackupError and not SubdomainError
2015-11-06 18:08:25 -08:00
7510c9fe29
Fix typo
2015-09-21 15:57:06 -07:00
78a1d53728
copy old backup as failed/errored apps
...
This ensures that
a) we don't get emails from janitor about bad app backups
b) that the backups are persisted over the s3 lifecycle
Fixes #493
2015-09-21 15:03:10 -07:00
e9b078cd58
add backups.copyLastBackup
2015-09-21 14:14:43 -07:00
baecbf783c
journalctl seems to barf on this debug
2015-09-15 20:50:22 -07:00
b4a34e6432
Explicity debug the fields
...
for some reason, journalctl barfs on this line
2015-09-15 14:55:20 -07:00
212d0bd55a
Revert "Add hack for broken app backup tarballs"
...
This reverts commit 9723951bfc
2015-08-31 21:44:24 -07:00
712ada940e
Add hack for broken app backup tarballs
2015-08-31 18:58:38 -07:00
a04740114c
Generate app restore urls locally
2015-08-26 09:11:28 -07:00
60b5d71c74
appBackupIds are not needed for backup url generation
2015-08-26 09:06:45 -07:00
444258e7ee
backupKey is a function
2015-08-25 18:37:51 -07:00
9fdcd452d0
Use locally generate signed urls for app backup
2015-08-25 17:52:01 -07:00
c63065e460
Also send the sessionToken when using the pre-signed url
2015-08-25 17:52:00 -07:00
c9bc5fc38e
Use signed urls for upload on the box side
2015-08-25 17:52:00 -07:00
77248fe65c
Construct backupUrl locally
2015-08-25 17:51:59 -07:00
df9d321ac3
app.portBindings and newManifest.tcpPorts may be null
2015-07-20 00:10:36 -07:00
Girish Ramakrishnan