🎨 Making service start progress UI user readable

[GitHK]

What do these changes do?

• Renamed progress element details to make it more user friendly for non developer users.
• Items are now displayed in the order they are done in the backend

Related issue/s

How to test

Dev Checklist

• No ENV changes or I properly updated ENV (read the instruction)

DevOps Checklist

[pcrespov]

thx

[elisabettai]

Following the suggestion from @mguidon here, I'd just show these steps:

1. Installing platform services...
2. Increasing system capacity...
3. Installing software...
4. Downloading files...

For our (dev) understanding

1. corresponds to pulling sidecar (which is normally very fast)
2. corresponds to autoscaling
3. corresponds to pulling images
4. corresponds to download outputs+state+inputs (users don't care about what exactly is being downloaded, but it would be nice if they understand that the more/bigger files they have, the slower this step will be.

[matusdrobuliak66]

👍

[GitHK]

Following the suggestion from @mguidon here, I'd just show these steps:

1. Installing platform services...
2. Increasing system capacity...
3. Installing software...
4. Downloading files...

For our (dev) understanding

1. corresponds to pulling sidecar (which is normally very fast)
2. corresponds to autoscaling
3. corresponds to pulling images
4. corresponds to download outputs+state+inputs (users don't care about what exactly is being downloaded, but it would be nice if they understand that the more/bigger files they have, the slower this step will be.

@elisabettai I'm not sure how to deal with the removal of the sections without crashing the FE. I would leave that part to someone with more Javascript experience. If it is really required to hide those parts.

[elisabettai]

Following the suggestion from @mguidon here, I'd just show these steps:

1. Installing platform services...
2. Increasing system capacity...
3. Installing software...
4. Downloading files...

For our (dev) understanding

1. corresponds to pulling sidecar (which is normally very fast)
2. corresponds to autoscaling
3. corresponds to pulling images
4. corresponds to download outputs+state+inputs (users don't care about what exactly is being downloaded, but it would be nice if they understand that the more/bigger files they have, the slower this step will be.

@elisabettai I'm not sure how to deal with the removal of the sections without crashing the FE. I would leave that part to someone with more Javascript experience. If it is really required to hide those parts.

I see @GitHK , I thought that the file you edited was the only place where those steps were defined and that was relatively easy to test if you were to break the FE.

I've also added some proposal for rephrasing some of the messages.

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud