John Keech

There have been some other scenarios discussed internally where this would be useful, such as building IDE indexes based on the source code which can't be done at image build...

This proposal has been implemented! #181 is tracking finalization of this proposal and is a good place to leave feedback/comments.

My preference is to keep it as simple as possible and not overcomplicate things. I like the proposed array syntax with the full options object inside if we are sticking...

@chrmarti how would complex objects get passed in and parsed by the install script? I think it will end up being more complicated for both end users and feature authors...

Just curious, is there a reason we'd prefer space as a delimiter over another character (such as a comma)?

>I would be amazing if there was some way to pass GitHub Secrets (repo or org scope) during each feature that needs it. @metaskills For Codespaces, secrets are set as...

>This would also allow encoding of this information in images to improve distribution of pre-build images. When the dev container CLI is used to build the image, these labels would...

Just to clarify, Dockerfiles are still fully supported. It's just more an an advanced use case, and we don't want people to have to be Docker experts in order to...

I'm not sure about the local test execution, but the one in the action shows the following error: https://github.com/snebjorn/devcontainer-feature/actions/runs/3193079539/jobs/5211272135#step:4:151 `./install.sh: 15: Bad substitution` That maps to this line in the...

I'm in favor of renaming it to `docker-outside-of-docker`. We just need to figure out the rename story in general for features. I don't think we'd want to publish it under...