1490705 - Re-add aws-provisioner-staging UI

Status: RESOLVED FIXED

(Taskcluster :: UI, enhancement)

Description

[John Ford [:jhford] CET/CEST Berlin Time]

This page was removed from tools.tc.net unexpectedly.  It's really important for validating EC2-Manager and AWS-Provisioner deployments.  Since this page is not on the landing screen for tools.tc.net, it shouldn't have much impact.

Comment 1

[Hassan Ali (:hassan)]

The aws-provisioner-staging UI was removed for redeployability in [1]. I'm not sure we know how to make the staging provisioner fit with rootUrl.

11:13 AM <dustin> so yes, I think it could be hacked in with baseUrl, but it's tricky - it's not just reverting that patch
11:14 AM <dustin> I'm not sure it's a useful use of time to figure that out, vs. a workaround

[1] https://github.com/taskcluster/taskcluster-tools/commit/46b8ccb2f209f4dc7a5ea667be29d0233a9b82b5#diff-8ac7aa44d05c324b2d70142f78eaf537

Comment 2

[John Ford [:jhford] CET/CEST Berlin Time]

It's really important for verifying provisioner deployments, and also for those working on staging worker types.  Can we redeploy the non-rooturl version using a baked in url?  Since this is not an exposed feature, it doesn't make much difference if it breaks for other deployments.

Or, since this is deployed as a Heroku app, is it possible to make a temporary app like tools-old.herokuapp.com which has the old version with the staging dashboard?

Comment 3

[Dustin J. Mitchell [:dustin] (he/him)]

Here's what I did to get this working:

$ git checkout 46b8ccb2f2^
$ yarn
$ yarn start

then hit http://localhost:9000 (well, I use an ngrok tunnel, but that's not necessary).  Do the development sign-in thing and you're on your way.

It probably wouldn't be too hard to do a similar thing and deploy to Heroku, if you'd like to do so.  I don't think anything in the deployment configuration has changed since that revision.