AlanLonguet
AlanLonguet
Ok I'll add a minio provider for the datastore, I think I'll keep the AWS oriented provider though since I don't think minio-go handles the seamless authentication through workload identity
https://github.com/padok-team/burrito/issues/318 just for tracking on our end
@faelau Oh it seems to be supported : https://github.com/minio/minio-go/pull/1944 I'll experiment with it and if it's ok might replace the aws sdk entirely
That's weird you should have at least some logs to explain that 500
Oh I see there's no error logging on the datastore side will fix that
Thanks for the suggestion same answer as the Apply Now : https://github.com/padok-team/burrito/issues/311#issuecomment-2227883953
Hey @seboudry we used cloud provider buckets as a backend storage so users can setup their own lifecycle policy would that be something ok for you ? For the number...
We wanted to make it configurable (Number of last runs/plans/apply) but didn't have time to ship it in a good condition so for now we compromised on 5
The retention of pods is tied up to the retention of TerraformRun resources, we rely on `ownerReferences` for their deletion, if you want to keep less pods you can use...
But I agree with you we need a better control on the history capabilities of the datastore that's something that needs to be enhanced