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
Note: If we implement option 1 from #211, we could punt this feature for the time being.
This feature is a pre-requisite for generating a computed devcontainer.json for use by e.g. coder modules. This can help resolve issues like #68 where a list of extensions needs to be available during installation of vscode, code-server, etc.
This commands main purpose is to output a merged configuration based on the projects devcontainer.json as well as configuration introduced by features.
A logical approach would be to mimic @devcontainer/cli output. Doing so would make envbuilder a versatile tool for interpreting devcontainer features, and potentially a drop-in single binary alternative.
Here's an example output from @devcontainer/cli when run against the microsoft/vscode repo.
Under .configuration the only new field is .configuration.configFilePath. Otherwise this is the project devcontainer.json as-is. The rest: .workspace, .featuresConfiguration and .mergedConfiguration are all added by read-configuration (and the merged config flag).
For this issue, we're mainly interested in implementing .mergedConfiguration.
@mafredri Would this achieve something similar to what I'm currently doing in a sidecar container? I would love to help implement this but don't really know whether you are looking for outside help on these
Note: If we implement option 1 from #211, we could punt this feature for the time being.
This feature is a pre-requisite for generating a computed
devcontainer.json
for use by e.g. coder modules. This can help resolve issues like #68 where a list of extensions needs to be available during installation ofvscode
,code-server
, etc.This commands main purpose is to output a merged configuration based on the projects
devcontainer.json
as well as configuration introduced by features.A logical approach would be to mimic
@devcontainer/cli
output. Doing so would makeenvbuilder
a versatile tool for interpreting devcontainer features, and potentially a drop-in single binary alternative.Here's an example output from
@devcontainer/cli
when run against themicrosoft/vscode
repo.devcontainer read-configuration --include-merged-configuration --log-format json --workspace-folder /tmp/envbuilder/vscode
Under
.configuration
the only new field is.configuration.configFilePath
. Otherwise this is the projectdevcontainer.json
as-is. The rest:.workspace
,.featuresConfiguration
and.mergedConfiguration
are all added byread-configuration
(and the merged config flag).For this issue, we're mainly interested in implementing
.mergedConfiguration
.Reference:
Logs (for reference)
The text was updated successfully, but these errors were encountered: