Files
openidea/plugins/official/container-runner
l0ng-ai 74e66a5dae feat(plugins): environment and debugger for plugin run configurations (API 1.9) (#3476)
Plugin run configurations could not set environment variables, and Debug
only worked when a source file in the arguments let the IDE infer a
debugger, so a plugin could run `func start` for an Azure Functions app but
not debug the worker it starts.

API 1.9 adds the optional `launch-configurations` export, preferred over
`run-configurations` when a component has both. Each configuration can add
environment variables (only names the IDE's environment doesn't already
have, like `process` commands) and name a debugger: launch the program
under a language's debugger, or run it and attach to the first process of
an Attach to Process kind that the run starts. Only the run's own
descendants are candidates; the IDE waits up to a minute while the run
lasts and otherwise leaves it running without the debugger. Remote projects
resolve the process on the server.

The SDK gets `LaunchConfigurations` / `launch_configurations`, the README
and docs describe the export, and the bundled components and fixtures are
rebuilt for 1.9.
2026-11-15 11:01:12 +08:00
..
2026-11-09 08:40:40 +08:00

container-runner — API 1.4 example

Put this directory on PATH before installing/granting the plugin, so process:openidea-example-wrapper resolves to the included executable. Run Example: Register Container Wrapper in a trusted project. It registers a project run target, opens a keyed terminal, writes an Output channel and sets a window status item. The owned terminal-exited event updates that window. Disable withdraws the target; terminal/output lifetimes follow the host rules. The fake wrapper just executes argv locally and exits its demo terminal.

To adapt it to DDEV, declare process:ddev, change program to ddev, args to ["exec"], and use command overrides such as ("composer", ["composer"]). For Lando declare process:lando and supply its CLI's command prefixes. Only approved executables run; selecting one in Settings › Plugins reapproves/pins it. No shell command strings are evaluated. For mapped working directories set container_root and workdir_args using your wrapper's documented argv convention (for example --cwd {cwd}), or let the wrapper manage cwd. Environment forwarding also belongs to that wrapper.

Build from the repository root:

plugins/build.sh official/container-runner
cargo test --manifest-path plugins/official/container-runner/Cargo.toml
cargo run -p ide-host --bin openidea-plugin -- check plugins/official/container-runner

Install the built package folder through Settings › Plugins › Install from Disk. See the plugin guide and official/community policy.

On Windows, supply an equivalent approved executable; the included demo script requires a POSIX shell. The host API itself is cross-platform.