Raúl Barroso

Epic: Better onboarding experience

1

This issue encompasses: - CLI command for `conduit init` which creates a template pipeline configuration file based on the chosen source and destination (quick and dirty + patch release, to...

As discussed in [this design document,](https://github.com/ConduitIO/conduit/discussions/1642) a Conduit CLI is what we believe should provide the developer experience our Conduit users need. This issue will tackle all the necessary work...

This is a placeholder created on Conduit's repository so we could tie it to the 0.13 release however, won't necessarily be _released_. Here some issues we've identified already: - [...

Feature: Force stop. Pipeline status should be stopped, not degraded

1

### Feature description When a user tries to force stop a pipeline, the result is that the status of the pipeline ends up being `degraded` and not `stopped`. I think...

### Description Looking at https://github.com/psviderski/unregistry this morning, I realized that we could add a link to the video so it's rendered inline for those who don't want to read. The...

### Feature description At the time of writing, a pipeline can only be initialized using builtin plugins. We should extend this limitation.

### Feature description On [Conduit v.0.12.0](https://conduit.io/changelog/2024-10-10-conduit-0-12-0-release), we provided the ability to automatically recover from errors. In Conduit, a [fatal error](https://github.com/ConduitIO/conduit/blob/main/pkg/foundation/cerrors/fatal.go) causes the pipeline to go into a [degraded state automatically](https://github.com/ConduitIO/conduit/blob/main/pkg/lifecycle/service.go#L780-L784),...

Improvements on pipeline architecture v2

1

As part of releasing [Conduit v0.12.2](https://github.com/ConduitIO/conduit/issues/1950), we wanted to bring https://github.com/ConduitIO/conduit/pull/1913, but there were some comments posted by @hariso that remained _un addressed_. Here are the ones I identified from...

Bug: Pipeline status `stopped` in a configuration file still runs the pipeline

2

### Bug description This pipeline with the status `stopped` shouldn't run: ```yaml version: "2.2" pipelines: - id: example-pipeline status: stopped name: "test" connectors: - id: example-source type: source plugin: "generator"...