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
Currently the devcontainers read-configuration command has two modes. One that shows the contents of devcontainer.json and one that also shows the feature configuration for any features referenced (via the --include-features-configuration).
However, what would be most useful would be a way to get a merged configuration inclusive of both out of the CLI. For example, adding a --effective-configuration flag:
This would be extremely useful for tool or service implementors that need to any pre-processing steps prior to starting a dev container, or need to inject contents based on the configuration.
As a concrete example, we could use this to modify the tools-vscode-server example under example-usage in this repository to adapt to customizations.vscode.settings and customizations.vscode.extensions through the use of jq and some shell scripts. Right now you'd have to manually parse each feature and do a merge yourself - which could deviate from the standard logic.
The text was updated successfully, but these errors were encountered:
Currently the
devcontainers read-configuration
command has two modes. One that shows the contents ofdevcontainer.json
and one that also shows the feature configuration for any features referenced (via the--include-features-configuration
).However, what would be most useful would be a way to get a merged configuration inclusive of both out of the CLI. For example, adding a
--effective-configuration
flag:This would be extremely useful for tool or service implementors that need to any pre-processing steps prior to starting a dev container, or need to inject contents based on the configuration.
As a concrete example, we could use this to modify the
tools-vscode-server example
underexample-usage
in this repository to adapt tocustomizations.vscode.settings
andcustomizations.vscode.extensions
through the use ofjq
and some shell scripts. Right now you'd have to manually parse each feature and do a merge yourself - which could deviate from the standard logic.The text was updated successfully, but these errors were encountered: