aboutsummaryrefslogtreecommitdiff
path: root/src/garage/admin.rs
Commit message (Collapse)AuthorAgeFilesLines
* Implement CreateBucketAlex Auvolat2022-01-051-8/+2
|
* Implement key allow|deny --create-bucketAlex Auvolat2022-01-051-0/+30
|
* Small changes in key model and refactoringnew-bucketsAlex Auvolat2022-01-041-6/+15
|
* New buckets for 0.6.0: make bucket id a SK and not a HK, CLI updatesAlex Auvolat2022-01-041-5/+5
|
* New buckets for 0.6.0: small changesAlex Auvolat2022-01-041-5/+11
| | | | | | | | | | | | - Fix bucket delete - fix merge of bucket creation date - Replace deletable with option in aliases Rationale: if two aliases point to conflicting bucket, resolving by making an arbitrary choice risks making data accessible when it shouldn't be. We'd rather resolve to deleting the alias until someone puts it back.
* Refactor logic for setting/unsetting aliasesAlex Auvolat2022-01-041-353/+129
|
* Remove website redirectsAlex Auvolat2022-01-041-1/+1
|
* Some movement of helper code and refactoring of error handlingAlex Auvolat2022-01-041-30/+34
|
* New buckets for 0.6.0: fix model and migrationAlex Auvolat2022-01-041-2/+4
|
* New buckets for 0.6.0: small fixes, including:Alex Auvolat2022-01-041-53/+102
| | | | | | | | - ensure bucket names are correct aws s3 names - when making aliases, ensure timestamps of links in both ways are the same - fix small remarks by trinity - don't have a separate website_access field
* More complete output to bucket info and key infoAlex Auvolat2022-01-041-23/+78
|
* New buckets for 0.6.0: migration code and build filesAlex Auvolat2022-01-041-0/+19
|
* Model changesAlex Auvolat2022-01-041-22/+29
|
* Implement bucket alias and bucket unaliasAlex Auvolat2022-01-041-0/+187
|
* New model for bucketsAlex Auvolat2022-01-041-208/+337
|
* Make table name a const in traitAlex Auvolat2021-12-151-1/+1
|
* Improve how node roles are assigned in Garagev0.5-beta1Alex Auvolat2021-11-161-2/+2
| | | | | | | | | | | | | | | | | - change the terminology: the network configuration becomes the role table, the configuration of a nodes becomes a node's role - the modification of the role table takes place in two steps: first, changes are staged in a CRDT data structure. Then, once the user is happy with the changes, they can commit them all at once (or revert them). - update documentation - fix tests - implement smarter partition assignation algorithm This patch breaks the format of the network configuration: when migrating, the cluster will be in a state where no roles are assigned. All roles must be re-assigned and commited at once. This migration should not pose an issue.
* Safety: never voluntarily delete block in 10min interval after RC reaches zeroAlex Auvolat2021-11-081-1/+1
|
* Improve CLI, adapt tests, update documentationAlex Auvolat2021-10-251-0/+504