garage.git - S3-compatible object store for small self-hosted geo-distributed deployments

	Commit message (Collapse)	Author	Age	Files	Lines
*	Implement {Put,Get,Delete}BucketCors and CORS in general	Alex Auvolat	2022-01-24	1	-0/+12
\| \| \| \| \| \|	- OPTIONS request against API endpoint - Returning corresponding CORS headers on API calls - Returning corresponding CORS headers on website GET's
*	New buckets for 0.6.0: small changes	Alex Auvolat	2022-01-04	1	-6/+0
\| \| \| \| \| \| \| \| \| \| \| \|	- 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.
*	New buckets for 0.6.0: fix model and migration	Alex Auvolat	2022-01-04	3	-8/+31
\|
*	Add must_use to some CRDT functions	Alex Auvolat	2022-01-04	3	-1/+3
\|
*	New buckets for 0.6.0: documentation and build files	Alex Auvolat	2022-01-04	1	-0/+11
\|
*	New buckets for 0.6.0: small fixes, including:	Alex Auvolat	2022-01-04	2	-20/+49
\| \| \| \| \| \| \| \|	- 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
*	Model changes	Alex Auvolat	2022-01-04	1	-0/+11
\|
*	New model for buckets	Alex Auvolat	2022-01-04	4	-4/+87
\|
*	Improve how node roles are assigned in Garagev0.5-beta1	Alex Auvolat	2021-11-16	6	-0/+514
	- 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.