Pipeline Assistant
The Cloud pipeline assistant helps you create, explain, and repair pipeline configuration. It works with the current YAML and your conversation, and can retrieve component, transformation-language, and example documentation.
Use it when you need help selecting a component, writing a transformation, or understanding a configuration error. You retain the normal editor and deployment workflow for reviewing and releasing the result.
Work with the current pipeline
- Open the pipeline editor and its assistant panel.
- Describe the source, transformation, and destination you need, or explain the error you are investigating.
- Review the proposed configuration and the assistant's validation feedback.
- Use Apply to place the proposed configuration into the editor.
- Inspect and test the result, then save or deploy it through the normal controls.
The assistant receives the current pipeline YAML as context. It can help refine an existing definition rather than requiring you to describe the whole pipeline again. Applying a suggestion changes the editor; it does not itself deploy to production.
Understand validation feedback
The assistant has a pipeline-validation tool that checks syntax, component types, field values, and required fields. If the validation service is unavailable, feedback can be limited to syntax checks. Treat that narrower result as such and run full validation when it is available.
Validation of a configuration does not prove source connectivity, authorization, destination writes, performance, or recovery behavior on your nodes. Test those properties in the intended environment.
Provide useful context
Include the shape of an example record, the desired output, and any constraints on the transformation. Use synthetic or redacted samples when records contain sensitive information. Avoid putting passwords, tokens, or raw secrets into the conversation or pipeline YAML.
Cloud receives the conversation and configuration used by the assistant. This is separate from the normal production record path through your edge nodes.
Continue through the standard release workflow
Assistant-generated YAML remains editable and can use the same validation, sample testing, versioning, deployment, and rollback processes as hand-authored configuration. See Pipeline authoring and Deployments and rollback.
The assistant depends on service availability and configuration. If it is unavailable, you can continue using the visual and YAML editors.
