Skip to content

Update develop-an-integration-as-an-api-service.md#1918

Open
ChamaliSandamini wants to merge 1 commit into
wso2:PEfrom
ChamaliSandamini:patch-1
Open

Update develop-an-integration-as-an-api-service.md#1918
ChamaliSandamini wants to merge 1 commit into
wso2:PEfrom
ChamaliSandamini:patch-1

Conversation

@ChamaliSandamini

Copy link
Copy Markdown

The "Develop an integration as an API service" guide was missing Step 2: Deploy the integration component. The steps jumped from Step 1 (Create) directly to Step 2 (Test), skipping the deployment step entirely. Additionally, the step numbering jumped from Step 2 directly to Step 4 with no Step 3.

Changes made:

  • Added missing Step 2: Deploy the integration component with all sub-steps
  • Renamed the existing Step 2 (Test the integration) to Step 3

Description

Describe the problems, issues, or needs driving this feature/fix and include links to related issues in the following format: Resolves issue1, issue2, etc.

Type of change

  • Change is only applicable for Developer view
  • Change is only applicable for Platform Engineer view
  • Change is applicable for both Developer and Platform Engineer views

Testing

  • Change is tested in Developer view
  • Change is tested in Platform Engineer view

Related issues

List related issues here

The "Develop an integration as an API service" guide was missing Step 2: Deploy the integration component. The steps jumped from Step 1 (Create) directly to Step 2 (Test), skipping the deployment step entirely. Additionally, the step numbering jumped from Step 2 directly to Step 4 with no Step 3.

Changes made:
- Added missing Step 2: Deploy the integration component with all sub-steps
- Renamed the existing Step 2 (Test the integration) to Step 3
@CLAassistant

CLAassistant commented May 26, 2026

Copy link
Copy Markdown

CLA assistant check
All committers have signed the CLA.

@coderabbitai

coderabbitai Bot commented May 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Summary

This PR updates the "Develop an integration as an API service" documentation guide by adding the previously missing Step 2: Deploy the integration component section.

Changes

  • Added Step 2: Deploy the integration component - New section with detailed console navigation steps and deployment status guidance, including guidance on automatic deployment behavior
  • Renumbered existing content - The previous Step 2 (Test the integration) is now Step 3 to reflect the correct workflow sequence

Impact

Restores the complete workflow documentation with all required steps in the correct order. The guide now properly guides users through the full integration development lifecycle: Create → Deploy → Test.

Lines changed: +16 / -1

Walkthrough

The PR updates the API service integration development guide by inserting a new Step 2 section that covers deploying the integration component. This section includes console navigation instructions and deployment status guidance, with a tip about automatic deployment. The previously numbered Step 2 (Test the integration) is renumbered to Step 3, shifting the remaining workflow steps accordingly. The change adds 16 lines and removes 1 line from the documentation file.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title is generic and vague; it does not clearly convey the specific change (adding a missing deployment step and renumbering). Consider using a more descriptive title such as 'Add missing Step 2: Deploy the integration component' to clearly communicate the primary change.
✅ Passed checks (4 passed)
Check name Status Explanation
Description check ✅ Passed The description clearly identifies the problems and changes made, but testing sections remain unchecked despite the template requiring them to be addressed.
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.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ 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 and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

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/developer-docs/docs/develop-components/develop-integrations/develop-an-integration-as-an-api-service.md`:
- Around line 45-55: The doc currently contradicts itself: Step 1 says "Create
and Deploy" performs deployment, while "Step 2: Deploy the integration
component" repeats deployment. Choose one clear workflow and update the text
accordingly: either change the Step 1 action text "Click Create and Deploy" to
"Click Create" (or "Create") and leave Step 2 as the single deploy flow, or keep
Step 1 as "Create and Deploy" and reword Step 2 to "Verify deployment / Redeploy
if needed" and change the bullets under "Step 2: Deploy the integration
component" to verification steps (e.g., open Deploy, view Build Area, confirm
Development card shows Deployment Status: Active). Apply the same resolution to
the repeated instance referenced in lines 60-62.
🪄 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: 177b6091-a68f-47af-8a43-f8d3985e18fa

📥 Commits

Reviewing files that changed from the base of the PR and between 905e96d and 4ea2a05.

📒 Files selected for processing (1)
  • en/developer-docs/docs/develop-components/develop-integrations/develop-an-integration-as-an-api-service.md

Comment on lines 45 to +55
8. Click **Create and Deploy**. {{ product_name }} initializes the component, builds it, and deploys it to the development environment.

## Step 2: Test the integration
## Step 2: Deploy the integration component

To deploy the integration component to the development environment, follow the steps given below:

1. In the {{ product_name }} Console left navigation menu, click **Deploy**.
2. In the **Build Area** card, click **Configure & Deploy**.
3. In the **Configurations** pane, click **Next**. This displays details of the endpoint ready to be deployed.
4. Click **Deploy**. This deploys the integration component to the development environment.
The **Development** card indicates the **Deployment Status** as **Active** when the integration is successfully deployed.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Resolve the deployment flow inconsistency between Step 1 and Step 2.

Line 45 says Create and Deploy already deploys the component, but Step 2 then asks the reader to deploy again. Please align these steps so the workflow has a single clear deployment action (for example, either change Step 1 to creation-only, or clarify Step 2 as verification/redeployment when needed).

Also applies to: 60-62

🧰 Tools
🪛 LanguageTool

[style] ~53-~53: Three successive sentences begin with the same word. Consider rewording the sentence or use a thesaurus to find a synonym.
Context: ... card, click Configure & Deploy. 3. In the Configurations pane, click **Ne...

(ENGLISH_WORD_REPEAT_BEGINNING_RULE)

🤖 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/developer-docs/docs/develop-components/develop-integrations/develop-an-integration-as-an-api-service.md`
around lines 45 - 55, The doc currently contradicts itself: Step 1 says "Create
and Deploy" performs deployment, while "Step 2: Deploy the integration
component" repeats deployment. Choose one clear workflow and update the text
accordingly: either change the Step 1 action text "Click Create and Deploy" to
"Click Create" (or "Create") and leave Step 2 as the single deploy flow, or keep
Step 1 as "Create and Deploy" and reword Step 2 to "Verify deployment / Redeploy
if needed" and change the bullets under "Step 2: Deploy the integration
component" to verification steps (e.g., open Deploy, view Build Area, confirm
Development card shows Deployment Status: Active). Apply the same resolution to
the repeated instance referenced in lines 60-62.

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