Skip to content

Check the Dify plugin in a native application - #946

Open
zlareb1 wants to merge 3 commits into
mainfrom
test/dify-native-application
Open

zlareb1 wants to merge 3 commits into
mainfrom
test/dify-native-application

Conversation

@zlareb1

@zlareb1 zlareb1 commented Nov 19, 2026 •

Copy link
Copy Markdown
Member

Changelog category (leave one):

  • CI Fix or Improvement

Changelog entry (one or two sentences a user of Loom can read without the diff; the release pull request collects these into the release notes):

The Dify plugin has a hosted application check for native tool registration and workflow execution.

Why

Archive and isolated tool tests do not exercise application setup, plugin discovery or workflow parameter binding. A disposable Community Edition deployment checks those boundaries against the candidate plugin and SDK wheel.

Scope and risk

The workflow starts the pinned official platform on a standard hosted Linux runner. It retains the security sidecars and signature verification, checks actual resource capacity before startup, and monitors bounded resource use. Insufficient capacity fails the job without changing its limits or deployment profile.

The scenario uses ordinary setup, login, workspace debugging and workflow routes. It checks remember, same-user recall, empty recall for a second user, shared knowledge search and the stored identity tuple. A fresh auth-on Loom fixture uses fake providers. Image-declared storage uses explicit owned volumes. Process generations, exact container ownership and scoped cleanup are checked; incomplete cleanup fails the job. Credentials are never written to stdout; retained logs and evidence use explicit redaction. No Cloud, marketplace acceptance or protected-session qualification is claimed.

Compatibility, rollout and rollback

  • Wire: no operations, fields or defaults change.
  • Operator steps: none. The new stack exists only on the disposable CI runner.
  • Rollback: revert the added check. No product schema, migrations or stored-data changes are introduced.

Tests

  • Ruff lint and format checks pass for the two scripts and test file.
  • Prettier checks pass for the workflow and Compose override; Python AST, prose and whitespace checks pass.
  • Twenty-two pure regressions cover Docker endpoint selection, archive membership, PID generation ownership, command retirement, late monitor failure native graph parameter binding, credential output, owned image volumes and bounded fixture readiness. A bounded local attempt was refused before workload by the shared test supervisor; these tests remain unrun locally and must pass in hosted CI.
  • Historical hosted runs passed 15 and then 19 guard cases plus exact archive/SDK checks. The later attempt reached fixture startup and ended on a connection reset, with verified cleanup. Readiness now handles transport failures within the unchanged deadlines, records its stage and preserves terminal permission refusals. New-head startup, workflows and cleanup remain unqualified; the hosted job must pass before merge. No local build, install or container stack ran.

AI assistance in the code (leave one; writing this description with AI is fine):

  • AI-generated: Codex prepared the workflow and checks. Independent source review runs alongside hosted CI.

  • I can explain every line of this diff and how it interacts with the rest of Loom.

Checklist

  • Required hosted checks pass. Local validation is limited to small checks related to this change.
  • The op reach manifest is regenerated for fixture calls. Wire, schema and coding-agent plugin files are unchanged.
  • No product migration, setting, operation or plugin behavior changes.
  • Application qualification is separate from package publication and marketplace acceptance.
  • Commits are signed off.

Exercise ordinary setup, discovery and scoped workflows with the candidate wheel and explicit owned cleanup on a disposable hosted runner.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Keep anonymous-volume refusal after mapping image storage to explicit project-owned volumes. Retain credentials only in memory and private files, and regenerate fixture operation reach.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>
Handle transport resets during readiness polling, keep permission refusals terminal, and record the failing startup stage without exposing response bodies.

Signed-off-by: zlareb1 <lareb.zafar@clickhouse.com>

This branch has not been deployed

No deployments
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