Consume configuration from extensions
bwateratmsft opened this issue · comments
The extensions will need to be able to configure some aspects of the container runtime clients. A few key ones come to mind:
- Path of the EXE, e.g. "docker" or "/usr/bin/docker"
- The base command, e.g. "docker-compose" vs. "docker compose"
- Human-readable name?
- Human-readable description?