feature: Enhance devcontainer for multi-language support and testing#68
Draft
feature: Enhance devcontainer for multi-language support and testing#68
Conversation
- Updated `.devcontainer/devcontainer.env.json` to enable additional languages: Java, Node.js, Ruby, C#, PHP, Rust, Kotlin, C, C++, JavaScript, and Go. - Modified `.devcontainer/devcontainer.json` to install the newly supported languages and tools, including their respective versions and features. - Added a new `bootstrap-toolbox.sh` script to install language-specific tools and link the Kubernetes generator. - Enhanced the `init` command in `cli/devopsos.py` to preserve existing `.devcontainer/` configurations and write generated output to `.devcontainer.generated/`. - Updated tests in `cli/test_cli.py` to verify the preservation of existing configurations and the correct generation of new files. - Revised documentation to reflect changes in the devcontainer setup and CLI command behavior.
- Introduced `devcontainer_templates.py` for generating devcontainer configurations using templates. - Added Dockerfile template for a multi-language development environment. - Created JSON templates for `devcontainer.env.json` and `devcontainer.json` to facilitate environment variable and configuration management. - Implemented functions for building environment configurations, features, arguments, extensions, and post-create commands. - Enhanced support for various programming languages, CI/CD tools, Kubernetes utilities, build tools, code analysis tools, and DevOps tools.
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
1 participant
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.
This pull request retires the repo-local devcontainer stack and transitions to a new, template-driven approach for generating devcontainer files. The legacy implementation has been archived, and related scripts and documentation have been removed or updated to reflect this change.
Devcontainer Stack Retirement and Migration:
.devcontainer/README.md: Updated to announce the retirement of the checked-in devcontainer stack, document the new template-based generation commands, and list the active source and legacy files. All legacy setup, configuration, and troubleshooting instructions have been removed..devcontainer/configure.py: Removed the configuration script that generated.devcontainer/devcontainer.jsonbased on.devcontainer/devcontainer.env.json..devcontainer/devcontainer.json: Removed the previously checked-in, static devcontainer configuration file.Legacy Implementation Archiving:
.devcontainer/Dockerfile→.legacy/devcontainer/Dockerfile: Moved the devcontainer Dockerfile to a legacy directory. Several language and tool installation sections (for Python, Java, JavaScript, Go, ESLint, Pylint) have been removed, and only unsupported language/toolchain installers remain. [1] [2] [3] [4] [5]These changes fully deprecate the old, static devcontainer setup in favor of a dynamic, template-based approach, and clean up legacy files and documentation accordingly.## Description
Type of Change
Changes Made
Testing Done
python -m pytest cli/test_cli.py mcp_server/test_server.py tests/test_comprehensive.py -v)Checklist