Conversation
…ure/CH-216-dev-containers
…to feature/CH-216-dev-containers
e49e952 to
82de5f8
Compare
…ure/CH-216-dev-containers
…loud-harness into feature/CH-216-dev-containers
This file contains hidden or 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.
Closes CH-216
Implemented solution
With this update, Cloud Harness provides a base image setup for vscode dev containers, and a blueprint dev container configuration to use it with new and existing projects.
The configuration includes, among the rest:
How to test this PR
Copy the
blueprint/.devcontainerdirectory in your project and use it.-> CTRL+SHIFT+P then "Reopen in container"
Sanity checks:
Breaking changes (select one):
breaking-changeand the migration procedure is well described abovePossible deployment updates issues (select one):
alert:deploymentTest coverage (select one):
Documentation (select one):
Nice to have (if relevant):