Deprecating the StreamPipes CLI and moving toward Dev Containers

[tenthe]

Hi everyone,

I’d like to get your feedback on the plan to deprecate the StreamPipes CLI as part of the next release.

I opened PR #4693, which marks the CLI as deprecated in the documentation and introduces the experimental Dev Container setup as the recommended direction for local development.

The CLI has been useful for setting up a local development environment for quite some time. However, it also contains a lot of legacy code and configuration that we need to keep maintaining. To reduce this complexity, I’d like to move the development setup closer to standard Docker Compose and Dev Container tooling.

The goal is not to remove functionality from developers. The existing Docker Compose files already describe the required services and dependencies, so developers who do not want to use VS Code or Dev Containers should still be able to use Docker Compose directly.

I’d really appreciate feedback from the community on this:

• Are there any important CLI use cases that would not be covered well enough by Docker Compose or the Dev Container setup?
• Does anyone have experience with Dev Containers and could provide feedback on the current setup?
• If you have already tried the Dev Container setup, what could be improved?

This is meant as a transition step. The CLI will remain available for now, but I’d like to communicate early that the proposed direction is to move toward Dev Containers and Docker Compose as the future development setup.

Looking forward to your thoughts.

Best,
Philipp

[dominikriemer]

+1
I also think the CLI never really was a CLI, more like a docker compose wrapper that we don't need anymore.