-
Notifications
You must be signed in to change notification settings - Fork 531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Suggestion] Add commands "Compose Logs" in command palette #2770
Comments
Restart and Down are available in the palette, albeit with slightly different names ("Docker: Compose Restart" and "Docker: Compose Down"). Logs is not, we should consider adding that. |
@bwateratmsft The commands "Docker: Compose Restart" and "Docker: Compose Down" in the command palette you mentioned above is for docker-compose.yml or docker-compose.debug.yml, but the one I mentioned is for Container group. When I try to executing "Docker: Compose Restart" and "Docker: Compose Down" commands, it require one project folder opening which contains docker-compose.yml file, we can select the docker-compose.yml file to continue this action. But I can right click container group and executing "Compose Restart/ Compose Down" without any folder opening. I guess they may be difference. Could you help to confirm this? |
Ah yes, you are totally right. Fixing the title. |
Unfortunately there is no good way to handle the user experience of showing the "Down" and "Restart" commands in the palette, since there are already such commands but targeted to files instead of running compose projects. Users would see two of the same command and we couldn't really explain how they were different. Logs is a new command, so it is possible to work it this way. Updated the title. |
This fix is now released with Docker extension version 1.12.0. |
OS: Ubuntu 18.04
Build Version: 20210310.1
Repro Steps:
Actual:
These commands don't exist in command palette.
Suggestion:
Add commands "Compose Logs/Compose Restart/ Compose Down" in command palette.
The text was updated successfully, but these errors were encountered: