Skip to content

Update AI Workspace documentation for July 2026 release - #359

Merged
Thushani-Jayasekera merged 5 commits into
wso2:mainfrom
Thushani-Jayasekera:aiws-docs
Jul 23, 2026
Merged

Update AI Workspace documentation for July 2026 release#359
Thushani-Jayasekera merged 5 commits into
wso2:mainfrom
Thushani-Jayasekera:aiws-docs

Conversation

@Thushani-Jayasekera

Copy link
Copy Markdown
Contributor
  • Updated last_updated dates across multiple files to reflect the new release date of July 23, 2026.
  • Revised setup instructions in "Getting Started" and "Setting Up AI Gateways" to point to version 1.0.0-beta for AI Workspace and 1.2.0-beta for AI Gateway.
  • Enhanced the "Overview" and "Authentication" sections to clarify the shared configuration file and authentication modes.
  • Added details on custom LLM provider templates and updated authentication type options in the LLM providers documentation.
  • Included new sections on custom policies and configuration interpolation in the relevant documentation files.

- Updated last_updated dates across multiple files to reflect the new release date of July 23, 2026.
- Revised setup instructions in "Getting Started" and "Setting Up AI Gateways" to point to version 1.0.0-beta for AI Workspace and 1.2.0-beta for AI Gateway.
- Enhanced the "Overview" and "Authentication" sections to clarify the shared configuration file and authentication modes.
- Added details on custom LLM provider templates and updated authentication type options in the LLM providers documentation.
- Included new sections on custom policies and configuration interpolation in the relevant documentation files.
@coderabbitai

coderabbitai Bot commented Jul 23, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@Thushani-Jayasekera, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 46 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 7acff536-4728-4e81-979b-f12d28055380

📥 Commits

Reviewing files that changed from the base of the PR and between 56958a6 and 967b19e.

📒 Files selected for processing (8)
  • en/docs/next/ai-workspace/ai-gateways/setting-up.md
  • en/docs/next/ai-workspace/authentication/asgardeo-setup.md
  • en/docs/next/ai-workspace/authentication/overview.md
  • en/docs/next/ai-workspace/getting-started.md
  • en/docs/next/ai-workspace/llm-providers/configure-provider.md
  • en/docs/next/ai-workspace/llm-providers/manage-provider.md
  • en/docs/next/ai-workspace/overview.md
  • en/docs/next/ai-workspace/policies/overview.md
📝 Walkthrough

Walkthrough

The documentation updates align AI Gateway installation instructions with v1.2.0-beta, update AI Workspace access to port 9643, and revise authentication configuration around shared config.toml tables and claim mappings. They also document provider authentication options, AWS Bedrock availability, API key prefixes, workspace settings, configuration interpolation, custom policies, and updated administrator credential setup guidance.

Suggested reviewers: krishanx92

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description is far too sparse for the template and omits nearly all required sections and details. Add the required sections from the template, especially Purpose, Checklist, Goals, Approach, Release note, Documentation, and test/security details.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly summarizes the main change: updating AI Workspace docs for the July 2026 release.
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.

- Revised setup instructions in "Getting Started" to point to the new version 1.0.0-beta.
- Added raw markdown tags in "Overview" for better formatting of configuration interpolation examples.

@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: 2

🤖 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/authentication/asgardeo-setup.md`:
- Line 171: Update the claim-mapping documentation near the referenced sentence
to distinguish Asgardeo token mapper configuration from the two service mapping
tables in config.toml. State that only [ai_workspace.auth.claim_mappings] and
[platform_api.auth.claim_mappings] are defined in config.toml, while the token
mapper output is configured in Asgardeo, and retain consistent claim names
across all three locations.

In `@en/docs/next/ai-workspace/getting-started.md`:
- Line 22: Update the download and directory-change commands in the
getting-started setup flow to replace every 1.0.0-alpha2 artifact reference with
1.0.0-beta, including the additionally affected occurrence, so all commands
consistently target the documented beta release.
🪄 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 Plus

Run ID: db1ee9be-ae93-4b47-85f6-911541735961

📥 Commits

Reviewing files that changed from the base of the PR and between 70b9f37 and 56958a6.

📒 Files selected for processing (10)
  • en/docs/next/ai-workspace/ai-gateways/setting-up.md
  • en/docs/next/ai-workspace/authentication/asgardeo-setup.md
  • en/docs/next/ai-workspace/authentication/overview.md
  • en/docs/next/ai-workspace/getting-started.md
  • en/docs/next/ai-workspace/llm-providers/configure-provider.md
  • en/docs/next/ai-workspace/llm-providers/manage-provider.md
  • en/docs/next/ai-workspace/llm-providers/overview.md
  • en/docs/next/ai-workspace/llm-proxies/manage-proxy.md
  • en/docs/next/ai-workspace/overview.md
  • en/docs/next/ai-workspace/policies/overview.md

Comment thread en/docs/next/ai-workspace/authentication/asgardeo-setup.md Outdated
Comment thread en/docs/next/ai-workspace/getting-started.md
…entication images

- Changed image paths in "Getting Started," "Asgardeo Setup," and "Overview" sections to point to the updated standalone AI Workspace directory.
- Clarified claim mapping consistency in the "Asgardeo Setup" section.
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