Mirror/MinIO - MinIO - Gitea

Author	SHA1	Message	Date
Harshavardhana	0379d6a37f	fix: permissions for docker-compose	3 months ago
Harshavardhana	e2ed696619	fix: docker-compose link since latest release	3 months ago
Harshavardhana	ba9f0f2480	fix: attempt to fix CI/CD upgrade tests with docker-compose (#19926 )	1 year ago
Harshavardhana	96d226c0b1	remove frivolous log about abort-multipart failure in replication (#19413 )	1 year ago
Harshavardhana	4a425cbac1	cleanup scripts and apply shfmt (#17284 )	2 years ago
Harshavardhana	ed5b67720c	rename deprecated 'mc policy' -> 'mc anonymous' (#15779 )	3 years ago
Aditya Manthramurthy	4c0f48c548	Add role ARN support for OIDC identity provider (#13651 ) - Allows setting a role policy parameter when configuring OIDC provider - When role policy is set, the server prints a role ARN usable in STS API requests - The given role policy is applied to STS API requests when the roleARN parameter is provided. - Service accounts for role policy are also possible and work as expected.	4 years ago
Harshavardhana	fee3f88cb5	use acceptedResponseStatusCode everywhere in HTTP logger (#13755 )	4 years ago
Harshavardhana	28f95f1fbe	quorum calculation getLatestFileInfo should be itself (#13717 ) FileInfo quorum shouldn't be passed down, instead inferred after obtaining a maximally occurring FileInfo. This PR also changes other functions that rely on wrong quorum calculation. Update tests as well to handle the proper requirement. All these changes are needed when migrating from older deployments where we used to set N/2 quorum for reads to EC:4 parity in newer releases.	4 years ago
Harshavardhana	c791de0e1e	re-implement pickValidInfo dataDir, move to quorum calculation (#13681 ) dataDir loosely based on maxima is incorrect and does not work in all situations such as disks in the following order - xl.json migration to xl.meta there may be partial xl.json's leftover if some disks are not yet connected when the disk is yet to come up, since xl.json mtime and xl.meta is same the dataDir maxima doesn't work properly leading to quorum issues. - its also possible that XLV1 might be true among the disks available, make sure to keep FileInfo based on common quorum and skip unexpected disks with the older data format. Also, this PR tests upgrade from older to a newer release if the data is readable and matches the checksum. NOTE: this is just initial work we can build on top of this to do further tests.	4 years ago