At the moment it isn't clear which is the smaller amount of work to undertake:

a)

• making relengapi-proxy redeployable
• updating all docker-worker workers to use the new version
• adding support for relengapi-proxy in generic-worker (in preparation for the docker-worker deprecation)

OR:

b)

• migrating all tasks off relengapi-proxy (some or all of this work is maybe being done by :garbas this quarter - although I'm not sure if that is only for release tasks)

Either one of these solutions will be needed for when we deploy to the new firefox ci deployment.

Hi Rok,

Can you confirm if you are migrating all tasks away from relengapi-proxy, or just release tasks / some other subset of the universe of all tasks.

Also, can you confirm anticipated delivery date, bugzilla tracking bug, etc?

Thanks!

:pmoore yes i'm confirming that we are migrating away from relengapi-proxy. basically we are migrating away from relengapi tokens and we will replace them with taskcluster authentication and therefore switching to taskcluster-proxy.

the estimate to get this done by the end of Q2, but who knows where I'll get stuck, Bug 1533330.

My understanding is that this doesn't block the migration to a new deployment, as relengapi-proxy could just as well be deployed there as in the current deployment.

m-c and m-b are not only using tc-proxy. after next release cycle i plan to retire relengapi-proxy.

Sounds good! It's not clear if this would be a blocker to redeploying Firefox CI, but having it done beforehand sounds likely and would be one less thing to worry about.

Rok, is this FIXED-able now?

relengapi style tokens are deprecated now.