Skip to content

Conversation

@filippomc
Copy link
Collaborator

@filippomc filippomc commented Nov 21, 2025

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:

  • pre installed cloud harness libraries and commands
  • set of predefined vscode plugins and configurations
  • persisted home directory
  • protected access to docker and kubernetes configurations from the host
  • aliases
  • some preinstalled dev utilities, libraries and shell tools

How to test this PR

Copy the blueprint/.devcontainer directory in your project and use it.
-> CTRL+SHIFT+P then "Reopen in container"

Sanity checks:

  • The pull request is explicitly linked to the relevant issue(s)
  • The issue is well described: clearly states the problem and the general proposed solution(s)
  • In this PR it is explicitly stated how to test the current change
  • The labels in the issue set the scope and the type of issue (bug, feature, etc.)
  • The relevant components are indicated in the issue (if any)
  • All the automated test checks are passing
  • All the linked issues are included in one Sprint
  • All the linked issues are in the Review state
  • All the linked issues are assigned

Breaking changes (select one):

  • The present changes do not change the preexisting api in any way
  • This PR and the issue are tagged as a breaking-change and the migration procedure is well described above

Possible deployment updates issues (select one):

  • There is no reason why deployments based on CloudHarness may break after the current update
  • This PR and the issue are tagged as alert:deployment

Test coverage (select one):

  • Tests for the relevant cases are included in this pr
  • The changes included in this pr are out of the current test coverage scope

Documentation (select one):

  • The documentation has been updated to match the current changes
  • The changes included in this PR are out of the current documentation scope

Nice to have (if relevant):

  • Screenshots of the changes
  • Explanatory video/animated gif

@filippomc filippomc changed the title Feature/ch 216 dev containers Dev containers Nov 21, 2025
@filippomc filippomc force-pushed the feature/CH-216-dev-containers branch from e49e952 to 82de5f8 Compare November 21, 2025 17:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants