1842209 - Migrate partials' `msbdiff-cache` off of the `auth:aws-s3` endpoint

Status: NEW

(Release Engineering :: Release Automation, task)

Description

[Andrew Halberstadt [:ahal]]

Partials generation tasks are using a caching mechansim that is relying on Taskcluster auth's aws-s3 endpoint. The bucket in question is tc-gp-private-1d-us-east-1.

This endpoint isn't going to work with GCS, so we need to figure out a different mechanism for caching these files that doesn't rely on it. We can either block on Taskcluster supporting similar functionality for GCS, or we can stop relying on Taskcluster for the auth and just use secrets or some other method instead.

Comment 1

[Andrew Halberstadt [:ahal]]

Tracking issue for supporting similar functionality in GCS:
https://github.com/taskcluster/taskcluster/issues/6381

Comment 2

[Yarik Kurmyza [:yarik] (he/him) (UTC+1)]

I think that endpoint will work just fine as long as auth service config is intact. And as far as I understand, it is only used as cache, for non-fxci artifacts, so no dependencies there.

Comment 3

[Andrew Halberstadt [:ahal]]

Yeah, I guess the description didn't make it clear that this bug is assuming we want to move off S3 entirely. It's possible we determine that this particular case is fine to leave in S3 indefinitely, in which case there's no action needed here.

Then again, there's talk of deprecating even the S3 endpoint in the above issue, so if that happens we'll have to migrate off of it eventually anyway.