26e33e7e07
paths are organized as follows:
project_id/segment_index/bucket_name/encrypted_key
so by picking parts[0] and parts[1], we were using the segment
index instead of the bucket name, causing bandwidth to be
accounted for incorrectly. additionally, we were using the
PUT action instead of the PUT_GRACEFUL_EXIT action, causing
the data to be charged incorrectly. we use PUT_REPAIR for
now because nodes won't accept uploads with PUT_GRACEFUL_EXIT
and our tables need migrations to handle rollups with it.
Change-Id: Ife2aff541222bac930c35df8fcf76e8bac5d60b2
|
||
|---|---|---|
| .. | ||
| chore_test.go | ||
| chore.go | ||
| common.go | ||
| db_test.go | ||
| db.go | ||
| endpoint_test.go | ||
| endpoint.go | ||
| getnodes_test.go | ||
| pathcollector.go | ||
| pending_test.go | ||
| pending.go | ||
| validation.go | ||