Add commands to console logs page

[JamesNK]

Description

Fixes #6626

Demo:

Checklist

• Is this feature complete?
  • Yes. Ready to ship.
  • No. Follow-up changes expected.
• Are you including unit tests for the changes and scenario tests if relevant?
  • Yes
  • No
• Did you add public API?
  • Yes
    • If yes, did you have an API Review for it?
      • Yes
      • No
    • Did you add <remarks /> and <code /> elements on your triple slash comments?
      • Yes
      • No
  • No
• Does the change make any security assumptions or guarantees?
  • Yes
    • If yes, have you done a threat model and had a security review?
      • Yes
      • No
  • No
• Does the change require an update in our Aspire docs?
  • Yes
    • Is this introducing a breaking change?
      • Yes
        • Link to aspire-docs issue (please use this breaking-change template):
      • No
        • Link to aspire-docs issue (please use this doc-idea template):
  • No

Microsoft Reviewers: Open in CodeFlow

[JamesNK]

Feels good to use. cc @davidfowl @DamianEdwards @leslierichardson95 in case you have any UI feedback.

[davidfowl]

This looks really good to me

[drewnoakes]

I wonder if some users will expect this to stop the logs, rather than the resource, which could be annoying or even dangerous (in ACA for example).

Some ideas that might help with this:

• Use a button with icon and text
• Move the start/stop button into the ... menu, so it always appears with text
• Move buttons next to resource combo box

[JamesNK]

The button icons and text come from the resource commands. Right now they just say Stop, Start, Restart. The text doesn't make it any clearer what the button does.

The buttons on the page could be removed and commands are only in a nested Resource commands menu.

e.g. to stop a resource, you would go ... -> Resource commands -> Stop

[davidfowl]

If we add log specific commands where would they go?

[JamesNK]

In the example above? Resource commands

[JamesNK]

The tooltip can say what the button does:

Is that enough to remove confusion?

[drewnoakes]

Only if the user reads the tool tip. Having a button that stops a resource without any confirmation that might be mistaken to do something else seems like it could cause some undue problems.

I'm thinking of the scenario where something is logging rapidly and the user wants to pause the logs to make it easier to read them, so they click the "stop" button thinking that's what it does.

What about splitting that "toolbar" area such that all resource related stuff is on one side (combo box, commands) and all log related stuff is on the other side (status, download, future pause/resume/clear buttons).

[JamesNK]

I don't see a good place to put command buttons on the left. If they were placed between the dropdown and status message it wouldn't look good because there can be a variable number of commands for a resource, and the status message location would jump around.

Edit: Maybe if the status was moved to the right then it could work.

[JamesNK]

How about this:

[JamesNK]

@adamint I believe these were left over from earlier iterations of logs download. I removed them and everything still seems to work

[drewnoakes]

How about this:

This is what I had in mind. Seeing it, I think it's much clearer.

[drewnoakes]

Any ideas on how we could localize these? Options including having the server send all translated values, or sending a known key value that's then looked up in the dashboard.

[JamesNK]

I don't think there is any plan for this kind of text to be localizable. Like state text, the API for adding commands just takes one string. That would need to change, and then I guess the server would need to send the frontend lang in a cookie or query string.