You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This iteration we aim to capture and create a base collection of "supported" configurations (encapsulated as dev container configurations) that represent different:
remote targets (eg: distro)
remote target configurations (eg: has curl installed but not wget)
VS Code settings (eg: changing the serverInstallPath from $HOME to a custom path)
Based on this catalog, we aim to concretely encode configurations that are compatible with the Remote SSH extension and track examples where support is not yet available. Additionally, this catalog may provide input data for an internal baseline suite or other automated tooling with the goal of increasing extension reliability. The resulting baseline must perform the same or better than the previous release to proceed with a new extension release.
Given the current complexity of the extension (both attempting to support endless remote configurations, and also providing dozens of VS Code user settings), focusing on reliability while still supporting a wide range of targets is our primary focus.
The text was updated successfully, but these errors were encountered:
This is a start to an initiative aimed at collecting a set of
configurations to represent Remote - SSH compatibility against a wide
variety of inputs, distros, etc.
Tooling has been built internally, based on the dev container CLI,
to exercise the extension against this (growing) list of configurations.
Stay tuned into the following iteration plans for more progress on this
initiative.
This is a start to an initiative aimed at collecting a set of
configurations to represent Remote - SSH compatibility against a wide
variety of inputs, distros, etc.
Tooling has been built internally, based on the dev container CLI,
to exercise the extension against this (growing) list of configurations.
Stay tuned into the following iteration plans for more progress on this
initiative.
This iteration we aim to capture and create a base collection of "supported" configurations (encapsulated as dev container configurations) that represent different:
serverInstallPath
from $HOME to a custom path)Based on this catalog, we aim to concretely encode configurations that are compatible with the Remote SSH extension and track examples where support is not yet available. Additionally, this catalog may provide input data for an internal baseline suite or other automated tooling with the goal of increasing extension reliability. The resulting baseline must perform the same or better than the previous release to proceed with a new extension release.
Given the current complexity of the extension (both attempting to support endless remote configurations, and also providing dozens of VS Code user settings), focusing on reliability while still supporting a wide range of targets is our primary focus.
The text was updated successfully, but these errors were encountered: