+++ This bug was initially created as a clone of Bug #1518927 +++

this would be an improvement over current explorer UI.

I started working on the worker manager ui, and I need a bit of a clarification on this. Currently in explorer, when you click on a provisioner in the list on the left, it will open an info card on the right. If you click on the provisioner name in the infocard, you'll see the list of the worker types (all worker types for that provisioner). Is that the functionality that you ask for?

Hi owlish!

Thanks for looking into this. CIDuty highlighted this as an issue in their worker / fleet management workflow. I believe the issue is that when going through the list of hardware Taskcluster workers through the Worker Explorer UI, you couldn't paginate or continue where you left off in the pool. Instead there was merely next/back buttons and often you would be taken back to the beginning of the pool.

I will be on parental leave starting tomorrow, April 10th and coming back June 11th. Could you please reach out to Danut Labici for further questions? I've cc'd the ciduty team to this bug.

@owlish are you still working on this? Does it block the tc-cloudops project?

[I duplicate this answer in the two similar tickets] Currently, I don't work on the UI because AWS provider is prioritized. I will return to the worker manager UI once I'm done with AWS provider. I don't think this blocks tc-cloudops migration.... However, maybe if you give me some background info on what prompted you to ask this question (i.e. what makes you think this might be blocking tc-migration; or to rephrase further, what are possible ways this can block the migration), I might be able to give more definitive answer

It's in the dependency tree for the "tc-cloudops" bug, is why I ask. I can fix that up. The way it might block the migration is my representing an existing functionality that users would lose during the migration if the bug isn't completed. I agree that it doesn't block the migration.

This will be handled in https://github.com/taskcluster/taskcluster/issues/2881