Principle:Langgenius Dify Pipeline Publishing
| Knowledge Sources | Dify |
|---|---|
| Domains | RAG, Pipeline, Frontend |
| Last Updated | 2026-02-12 00:00 GMT |
Overview
Description
Pipeline Publishing is the principle governing how RAG pipelines in Dify are finalized, shared, and distributed. Publishing transforms a configured pipeline from an editable draft into a reusable artifact that can be shared as a customized template, exported as a portable DSL file, or updated with revised metadata.
The publishing workflow supports three complementary operations:
- Publish as Customized Template -- Promotes a pipeline configuration into the customized template catalog, making it available for reuse by other users and projects. The published template includes a name, icon, and optional description, creating a branded, discoverable entry in the template library.
- Export Pipeline DSL -- Serializes the pipeline's complete configuration (graph, nodes, edges, variables) into a portable DSL format that can be downloaded, version-controlled, or transferred to another Dify instance. Supports an
include_secretoption for including or excluding sensitive credential data. - Update Template Info -- Modifies the metadata (name, icon, description) of an already-published customized template, enabling iterative refinement of template branding without re-publishing the full configuration.
Usage
Pipeline Publishing is relevant whenever a user:
- Has completed configuring and testing a RAG pipeline and wants to make it available as a reusable template for the team.
- Needs to export a pipeline configuration for backup, migration, or sharing with external collaborators.
- Wants to update the display name, icon, or description of an existing customized template.
- Is establishing organizational standards by publishing approved pipeline patterns as templates.
- Needs to transfer pipeline configurations between Dify instances (e.g., from staging to production).
Publishing is the final stage in the pipeline development lifecycle, following template selection, datasource configuration, processing setup, embedding/indexing configuration, and execution testing.
Theoretical Basis
Pipeline Publishing follows the Immutable Release pattern from software delivery practices. Once published, a template represents a versioned snapshot of the pipeline configuration. The separation between the mutable draft and the immutable published state ensures that:
- Stability -- Published templates are stable references that do not change when the source pipeline is further edited.
- Reproducibility -- Exporting as DSL enables exact reproduction of pipeline configurations across environments, aligning with Infrastructure as Code principles.
- Discoverability -- Publishing to the customized template catalog with structured metadata (name, icon, description) follows the Service Catalog pattern, making organizational knowledge easily findable.
The DSL export capability with the include_secret option demonstrates the Principle of Least Privilege applied to configuration portability: users can share pipeline structures without exposing authentication credentials. This separation between configuration and secrets is a security best practice in distributed systems.
The template metadata update operation supports Continuous Improvement by allowing template branding to evolve independently of the underlying pipeline logic, reducing friction in maintaining an up-to-date template catalog.