chore: fix the devcontainer configuration to work with local development containers and GitHub Codespaces #1316
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this does:
This changes the devcontainer configuration to work both in local VS Code containers as well as GitHub Codespaces. GitHub Codespaces do not support the
workspaceFolderoption yet, so after starting a Codespace we'd end up in a different folder that contained thenode-mssqlsource code, but did not have thetest/.mssql.jsonconfiguration properly set up.Instead of using a docker volume to map the
.mssql.jsonfile into the correct location, we just copy it over on container creation, unless it is already there.