No Branch/Tag Specified
new-layout-ux
next
main
increasing-timestamps
feat/website-redir
jepsen
smithy2
test/compilation
poc/nomad-ci
test-ci-wait
pnet_datalink-0.33.0
optimal-layout
k2v-watch-range
db-debug-log
build-convert-db
demonstrate-cargo2nix-bug
dangerous/no-fsync
dev0.7.3
doc/benchmarks
bug/check_static
bucket-cors-more
storage-optimizations
old-main
v0.8.4
v0.8.3
v0.8.1
v0.8.0
v0.8.0-rc2
v0.8.0-rc1
v0.7.3
v0.7.2.1
v0.7.2
v0.7.1
v0.3.0.1
v0.3.0
v0.2.1.5
v0.2.1
0.1.0
0.1.0b
0.1.1
0.1.1b
0.4-alpha
0.4-beta
format_table-v0.1.0
format_table-v0.1.1
v0.2.0
v0.3.0.2
v0.4-rc1
v0.4-rc2
v0.4.0
v0.5-beta1
v0.5.0
v0.5.0.1
v0.5.1
v0.6.0
v0.6.0-rc1
v0.6.1
v0.7.0
v0.7.0-rc1
v0.7.1-admin-k2v
v0.7.1-admin-k2v-2
v0.7.1-k2v
v0.7.2+ci-test-version
v0.7.2-k2v
v0.7.2_ci-test-2
v0.7.3-beta1
v0.7.3-beta2
v0.7.99-k2v
v0.7.99.1-k2v
v0.7.99.2-k2v
v0.7.99.3-k2v
v0.8.0-beta1
v0.8.0-beta1-k2v
v0.8.0-beta2
v0.8.0-beta2-k2v
v0.8.0-dangerous-no-fsync
v0.8.2
v0.8.3-rc1
v0.9.0-beta1
v0.9.0-beta2
Labels
Clear labels
Issues concerning the administration API
Issues with Nix, Drone, Rust Compiler, etc.
Issues of theoretical correctness that may impact edge-case scenarios
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims
For issues that we don't want to spend time on until made absolutely necessary
A bug that should be newcomer friendly.
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.
Apply labels
AdminAPI
Issues concerning the administration API
Bug
CI
Issues with Nix, Drone, Rust Compiler, etc.
Correctness
Issues of theoretical correctness that may impact edge-case scenarios
Critical
Documentation
Ideas
For abstract ideas/proposal to make Garage better, to better communicate our not yet achieved aims
Improvement
Low priority
For issues that we don't want to spend time on until made absolutely necessary
Newcomer
A bug that should be newcomer friendly.
Performance
S3 Compatibility
Testing
Usability
Propositions to make Garage easier to operate, by improving error reporting, CLI, etc.
No Label
AdminAPI
Bug
CI
Correctness
Critical
Documentation
Ideas
Improvement
Low priority
Newcomer
Performance
S3 Compatibility
Testing
Usability
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#166
Reference in New Issue
There is no content yet.
Delete Branch '%!s(<nil>)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
At the beginning of the development, I said it could be interesting to have a delay between the deletion of an object and its effective removal of the cluster. Such behavior can be achieved by enabling bucket versioning + adding a lifecycle policy.
Having these 2 features could enable many people to implement a backup strategy "for free", including us.
For example, currently I am investigating ways to backup Garage buckets by mirroring them on minio with s3s3mirror. By activating versioning on Minio + a lifecycle policy, it will be possible to restore any file during a given period (eg. 100 days) even if it has been wrongly deleted or modified by an operator, a faulty software or a user.
I have two usecases for a versioning system:
The simple backup described above, just to assist users who say "I accidentally deleted a file and I'd like it back please"
Thwarting any potential ransomware attacks that happen to figure out how to 'encrypt' files in an object store (though this would require that disabling the versioning to be additionally restricted to admin's only)