Conversation
📝 WalkthroughWalkthroughAdded comprehensive Boomi connector documentation and catalog entries: new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 inconclusive)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Fix all issues with AI agents
In `@baton/boomi.mdx`:
- Line 18: Replace the internal link string
"/docs/product/admin/account-provisioning" with the repository's standard
relative internal path format (remove the "/docs" prefix) so it matches other
links (e.g., use "/product/admin/account-provisioning" or the same relative form
other docs use); update the link text in the Boomi connector sentence
accordingly to keep link semantics unchanged.
🧹 Nitpick comments (4)
baton/_release-notes.mdx (1)
6-6: Incomplete release notes entry for Boomi.This comment appears to be a placeholder marker. Before merging, add a proper release notes entry for the Boomi connector, similar to other entries in this file (e.g., the OpenAI entry at lines 8-15 with an
<Update>block and<Card>component).Example structure:
<Update label="January 22, 2026"> ### New connectors <Columns cols={2}> <Card title="Boomi" href="/baton/boomi" horizontal icon="arrow-right" /> </Columns> </Update>baton/boomi.mdx (3)
1-7: Add editor refresh comment.Per documentation guidelines, MDX files should include an editor refresh comment. Based on learnings, add:
{/* Editor Refresh: YYYY-MM-DD */}after the frontmatter.Suggested addition after line 7
--- + +{/* Editor Refresh: 2026-01-22 */} ## Capabilities
202-204: Boolean value in KubernetesstringDatashould be quoted.In Kubernetes Secrets with
stringData, all values are strings. While YAML may accepttrueas a boolean, it's clearer and more correct to quote it to ensure it's treated as the string"true".Suggested fix
# Optional: include if you want ConductorOne to provision access using this connector - BATON_PROVISIONING: true + BATON_PROVISIONING: "true"
231-231: Consider pinning the container image to a specific version instead oflatest.Using
:latesttag can lead to unexpected behavior when the image is updated. For production deployments, consider recommending a specific version tag or noting that users should pin to a specific version.
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Fix all issues with AI agents
In `@baton/boomi.mdx`:
- Around line 1-7: Add the required editor refresh comment to the MDX doc titled
"Set up a Boomi connector": insert a single line comment in the format {/*
Editor Refresh: YYYY-MM-DD */} immediately after the frontmatter block (i.e.,
right before the document content begins) inside the MDX file, using the current
date in YYYY-MM-DD format so the editor refresh requirement is satisfied.
- Line 135: The Markdown link "https://github.com/ConductorOne/baton-boomi" in
the boomi connector instruction is invalid (404); either remove the hyperlink or
replace it with the correct repository URL. Locate the line containing the
string "Follow these instructions to use the
[Boomi](https://github.com/ConductorOne/baton-boomi) connector" and either (a)
point the bracketed Boomi link to the correct ConductorOne repo if one exists,
or (b) remove the link and leave plain text (e.g., "Boomi connector" without a
URL) and add a brief note that the connector is not available if no repo exists.
🧹 Nitpick comments (2)
baton/boomi.mdx (2)
202-204: Quote boolean value in stringData.In Kubernetes secrets with
stringData, the unquotedtrueis parsed as a YAML boolean before being converted to a string. For clarity and to avoid potential parsing issues, quote the value explicitly.Suggested fix
# Optional: include if you want ConductorOne to provision access using this connector - BATON_PROVISIONING: true + BATON_PROVISIONING: "true"
210-239: Consider noting image tag best practices.The deployment uses
image: ghcr.io/conductorone/baton-boomi:latest. While acceptable for documentation examples, you may want to add a brief note suggesting users pin to a specific version tag in production environments for reproducibility.
| --- | ||
| title: "Set up a Boomi connector" | ||
| og:title: "Set up a Boomi connector" | ||
| description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | ||
| og:description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | ||
| sidebarTitle: "Boomi" | ||
| --- |
There was a problem hiding this comment.
Missing Editor Refresh comment.
Per coding guidelines, MDX documentation files should include an editor refresh comment in the format {/* Editor Refresh: YYYY-MM-DD */}.
Suggested fix
---
title: "Set up a Boomi connector"
og:title: "Set up a Boomi connector"
description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access."
og:description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access."
sidebarTitle: "Boomi"
---
+
+{/* Editor Refresh: 2026-01-22 */}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| --- | |
| title: "Set up a Boomi connector" | |
| og:title: "Set up a Boomi connector" | |
| description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | |
| og:description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | |
| sidebarTitle: "Boomi" | |
| --- | |
| --- | |
| title: "Set up a Boomi connector" | |
| og:title: "Set up a Boomi connector" | |
| description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | |
| og:description: "ConductorOne provides identity governance and just-in-time provisioning for Boomi. Integrate your Boomi instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access." | |
| sidebarTitle: "Boomi" | |
| --- | |
| {/* Editor Refresh: 2026-01-22 */} |
🤖 Prompt for AI Agents
In `@baton/boomi.mdx` around lines 1 - 7, Add the required editor refresh comment
to the MDX doc titled "Set up a Boomi connector": insert a single line comment
in the format {/* Editor Refresh: YYYY-MM-DD */} immediately after the
frontmatter block (i.e., right before the document content begins) inside the
MDX file, using the current date in YYYY-MM-DD format so the editor refresh
requirement is satisfied.
| </Tab> | ||
|
|
||
| <Tab title="Self-hosted"> | ||
| Follow these instructions to use the [Boomi](https://github.com/ConductorOne/baton-boomi) connector, hosted and run in your own environment. |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
# Verify GitHub repository is accessible
curl -s -o /dev/null -w "%{http_code}" https://github.com/ConductorOne/baton-boomiRepository: ConductorOne/docs
Length of output: 64
🌐 Web query:
ConductorOne baton-boomi GitHub repository
💡 Result:
I couldn't find a ConductorOne repository named "baton-boomi." ConductorOne does publish the Baton toolkit and a GitHub connector (baton and baton-github). See their GitHub repos: baton and baton-github. [1][2]
If you want, I can run a broader web/GitHub search (or check a specific organization/account) to double-check.
Sources:
- ConductorOne/baton (Baton toolkit). [1]
- ConductorOne/baton-github (GitHub connector). [2]
🌐 Web query:
ConductorOne Boomi connector baton repository
💡 Result:
Short answer — ConductorOne’s Baton is an open-source connector toolkit (SDK + CLI + many prebuilt connectors) and its source is hosted on GitHub. Key repos and docs:
- Baton product page / overview. [1]
- Main GitHub repo: ConductorOne/baton (Apache‑2.0). [2]
- Example connector repo: ConductorOne/baton-github. [3]
- Baton connector docs and how to build custom connectors (including SCIM). [4]
If you want, I can: (a) link the specific GitHub repo URLs, (b) show how to install/run a Baton connector (e.g., baton-github), or (c) help plan a custom Baton connector for Boomi — which option do you want?
🏁 Script executed:
#!/bin/bash
# Check if there are any other variations of the Boomi connector
curl -s https://api.github.com/users/ConductorOne/repos 2>&1 | grep -i boomiRepository: ConductorOne/docs
Length of output: 43
Remove or correct the GitHub repository link — the baton-boomi repository does not exist.
The referenced GitHub repository https://github.com/ConductorOne/baton-boomi returns a 404 error and does not exist. Verify whether a Boomi connector exists under ConductorOne and provide the correct repository URL, or remove this link if the connector is not available.
🤖 Prompt for AI Agents
In `@baton/boomi.mdx` at line 135, The Markdown link
"https://github.com/ConductorOne/baton-boomi" in the boomi connector instruction
is invalid (404); either remove the hyperlink or replace it with the correct
repository URL. Locate the line containing the string "Follow these instructions
to use the [Boomi](https://github.com/ConductorOne/baton-boomi) connector" and
either (a) point the bracketed Boomi link to the correct ConductorOne repo if
one exists, or (b) remove the link and leave plain text (e.g., "Boomi connector"
without a URL) and add a brief note that the connector is not available if no
repo exists.
1 participant
Associated with Jira ticket DOCS-442
Do not merge until the connector is out of validation status.
Summary by CodeRabbit
New Features
Documentation
✏️ Tip: You can customize this high-level summary in your review settings.