Skip to content

Add AI Workspace DP to CP docs#327

Open
thivindu wants to merge 1 commit into
wso2:mainfrom
thivindu:ai-workspace-dp-cp
Open

Add AI Workspace DP to CP docs#327
thivindu wants to merge 1 commit into
wso2:mainfrom
thivindu:ai-workspace-dp-cp

Conversation

@thivindu

@thivindu thivindu commented Jul 7, 2026

Copy link
Copy Markdown

This pull request adds a comprehensive new guide to the documentation that explains how AI artifacts created on the AI Gateway are automatically synced to the AI Workspace as read-only copies. The guide covers the bottom-up sync process, including prerequisites, enabling and troubleshooting sync, supported artifact types, and detailed steps for creating and managing these artifacts.

New documentation: Bottom-up AI artifact sync

  • Added a new guide, bottom-up-ai-artifact-deployment-guide.md, detailing how to create AI artifacts (LLM Provider Template, LLM Provider, LLM Proxy, MCP Proxy) on the gateway and how they are synced as read-only copies to the AI Workspace.
  • Included step-by-step instructions for enabling sync, creating artifacts via the gateway management API, and viewing/managing them in the AI Workspace.
  • Clarified what can and cannot be changed in the AI Workspace for gateway-owned artifacts, and described the behavior when updating or deleting artifacts.
  • Provided troubleshooting guidance for common sync and artifact visibility issues.
  • Documented support for both mutable and immutable gateway modes, ensuring users understand sync behavior in all deployment scenarios.

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Added a new AI Workspace documentation guide for bottom-up AI artifact deployment from AI Gateway.

The guide explains:

  • How gateway-created artifacts are automatically synced into AI Workspace as read-only copies
  • Prerequisites and enabling/disabling sync
  • Supported artifact types and dependency ordering
  • Step-by-step creation examples through the gateway management API
  • How to find, view, and manage synced artifacts in AI Workspace
  • Which edits are allowed for gateway-owned artifacts
  • Update, delete, and resync behavior
  • How the flow works for immutable gateways
  • Troubleshooting for common sync and reconciliation issues

Walkthrough

This pull request adds a new documentation page describing bottom-up AI artifact deployment, explaining how artifacts created directly on an AI Gateway (LLM Provider Templates, LLM Providers, LLM Proxies, and MCP Proxies) are automatically synced to the AI Workspace as read-only copies. The guide covers prerequisites, the deployment_sync_enabled setting, sync rules, supported management API endpoints, step-by-step creation examples, workspace visibility, edit/delete semantics, reconciliation behavior, immutable gateway handling, and troubleshooting. No code entities are modified.

Sequence Diagram(s)

Not applicable — this change is documentation-only and does not introduce or modify functional control flow.

Suggested reviewers: Krishanx92

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description summarizes the change but does not follow the required template sections or checklist items. Add the required Purpose, Checklist, Goals, Approach, and other template sections, with issue links and completion details where applicable.
Title check ❓ Inconclusive The title is too abbreviated and vague, so it does not clearly describe the main documentation change. Use a concise title that spells out the AI Workspace bottom-up AI artifact sync documentation change.
✅ Passed checks (3 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@en/docs/next/ai-workspace/bottom-up-ai-artifact-deployment-guide.md`:
- Around line 65-68: The fenced ASCII diagram in the documentation is unlabeled,
which triggers markdownlint MD040. Update the affected diagram blocks in the
guide to use a text/plaintext fence label, or convert them to a non-fenced
block, and apply the same fix to the other matching diagram block referenced in
the comment so the docs lint passes cleanly.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 7fec275b-9a80-4390-88f2-ddc94c14c92a

📥 Commits

Reviewing files that changed from the base of the PR and between 388895d and e5dc003.

📒 Files selected for processing (1)
  • en/docs/next/ai-workspace/bottom-up-ai-artifact-deployment-guide.md

Comment on lines +65 to +68
```
Create on the gateway ─┬─▶ takes effect immediately (starts serving traffic)
└─▶ synced to the AI Workspace ─▶ appears as a read-only copy
```

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Label the plain fenced diagrams.

These unlabeled fences are triggering markdownlint MD040. Mark them as text/plaintext, or use a non-fenced block, so the docs lint passes cleanly.

Also applies to: 117-119

🧰 Tools
🪛 markdownlint-cli2 (0.22.1)

[warning] 65-65: Fenced code blocks should have a language specified

(MD040, fenced-code-language)

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@en/docs/next/ai-workspace/bottom-up-ai-artifact-deployment-guide.md` around
lines 65 - 68, The fenced ASCII diagram in the documentation is unlabeled, which
triggers markdownlint MD040. Update the affected diagram blocks in the guide to
use a text/plaintext fence label, or convert them to a non-fenced block, and
apply the same fix to the other matching diagram block referenced in the comment
so the docs lint passes cleanly.

Source: Linters/SAST tools

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.

1 participant