Skip to content

Conversation

sowen1023
Copy link
Contributor

@sowen1023 sowen1023 commented Oct 18, 2025

What does this PR do

  • 💎 Make connectors pipeline-based
  • 🔧 Fix feishu/lark connector UI problem
  • 🧩 Align relative reference documents to the connector pipeline-based
  • 🧩 Align the connector.tpl to the connector pipeline-based and path hierarchy

Standards checklist

  • ✅ The PR title is descriptive
  • ✅ The commit messages are semantic
  • ✅ Necessary tests are added
  • ✅ Updated the release notes
  • ✅ Necessary documents have been added if this is a new feature

@sowen1023
Copy link
Contributor Author

Except for Salesforce, all of the connectors had been tested. Please test again.

> Use `confluence` as a unique identifier, as it is a builtin connector.
## Update coco-server's config
> **Note**: Starting from version **0.4.0**, the Confluence connector uses a **pipeline-based architecture** for better performance and flexibility. The `processor` configuration is required for the connector to work properly.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0.4 ->0.9

queue:
name: indexing_documents
interval: 5m
Starting from version **0.4.0**, the Confluence connector uses a **pipeline-based architecture** instead of the legacy scheduled task approach. This provides:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here

### Architecture Design

#### Refactored Architecture
#### Refactored Architecture (v0.4.0)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

0.4?

}
```

#### Plugin Implementation
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These AI genereated sections should be removed.

> **Note**: Starting from version **0.4.0**, the Gitea connector uses a **pipeline-based architecture** for better performance and flexibility. The `processor` configuration is required for the connector to work properly.
Below is an example configuration for enabling the Gitea Connector in coco-server:
## Pipeline Architecture
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no need to repeat these pipeline arch and common pipeline configurations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants