Skip to content

Update ctl tool documentation#6172

Open
RovinKYK wants to merge 5 commits into
wso2:masterfrom
RovinKYK:master
Open

Update ctl tool documentation#6172
RovinKYK wants to merge 5 commits into
wso2:masterfrom
RovinKYK:master

Conversation

@RovinKYK
Copy link
Copy Markdown
Contributor

@RovinKYK RovinKYK commented Jun 3, 2026

Purpose

This PR updates CTL tool documentation to reflect the support added to new resource types and the logging improvements.

Related to https://github.com/wso2-enterprise/iam-product-management/issues/662

Related PRs

Test environment

Security checks

Copilot AI review requested due to automatic review settings June 3, 2026 06:44
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates IAM-CTL promotion documentation to cover additional resource types and clarify operational behavior via new logging and resource-specific guidance.

Changes:

  • Expanded supported IAM-CTL resource type list (with version-gated additions).
  • Added new documentation sections for unified logging and resource-type-specific caveats.
  • Embedded the new sections into multiple “promote configurations” pages across product/version docs.

Reviewed changes

Copilot reviewed 11 out of 11 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
en/includes/deploy/ctl-tool/resource-types-7.x.md Adds additional resource types and version-gated entries for IAM-CTL propagation docs.
en/includes/deploy/ctl-tool/resource-specific-notes.md New include documenting resource-specific import/export behaviors and caveats.
en/includes/deploy/ctl-tool/logging.md New include documenting IAM-CTL logging configuration and safety warning.
en/includes/deploy/ctl-tool/getting-started-7.x.md Extends required M2M application scopes list for newly supported resources, with version gating.
en/identity-server/next/docs/deploy/promote-configurations.md Includes the new logging and resource-specific notes sections.
en/identity-server/7.3.0/docs/deploy/promote-configurations.md Includes the new logging and resource-specific notes sections.
en/identity-server/7.2.0/docs/deploy/promote-configurations.md Includes the new logging and resource-specific notes sections.
en/identity-server/7.1.0/docs/deploy/promote-configurations.md Includes the new logging and resource-specific notes sections.
en/identity-server/7.0.0/docs/deploy/promote-configurations.md Includes the new logging and resource-specific notes sections.
en/identity-server/5.11.0/docs/setup/promote-configurations.md Adds a logging section directly (non-include) for 5.11.0 docs.
en/asgardeo/docs/guides/your-asgardeo/manage-environments/promote-configurations.md Includes the new logging and resource-specific notes sections.
Comments suppressed due to low confidence (1)

en/includes/deploy/ctl-tool/resource-types-7.x.md:1

  • The resource type list includes Email Templates unconditionally, but getting-started-7.x.md gates Email Template API scopes to server_version == \"7.0\" and uses Notification Template APIs for >= 7.1. To avoid conflicting guidance, align the resource type list with the same version gating (either gate Email Templates to the versions where it exists, or clarify how it maps to notification templates in newer versions).
### Supported resource types

Comment thread en/includes/deploy/ctl-tool/logging.md
Comment thread en/identity-server/5.11.0/docs/setup/promote-configurations.md
Comment thread en/includes/deploy/ctl-tool/getting-started-7.x.md
Comment thread en/includes/deploy/ctl-tool/resource-specific-notes.md Outdated
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 3, 2026

Review Change Stack

Warning

Review limit reached

@RovinKYK, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 13 minutes and 57 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 8a4d7279-7431-4630-ac0b-5297d3a5b75e

📥 Commits

Reviewing files that changed from the base of the PR and between d937673 and 7e33f82.

📒 Files selected for processing (1)
  • en/identity-server/5.11.0/docs/setup/promote-configurations.md
📝 Walkthrough

Walkthrough

Adds IAM-CTL logging documentation and resource-specific promotion notes as shared includes, expands ctl-tool reference docs (resource types and permissions), embeds logging in 5.11.0, and inserts include directives into multiple promote-configurations guides for consistent distribution.

Changes

CTL-Tool Documentation Enhancement

Layer / File(s) Summary
Create shared logging and resource-specific documentation
en/includes/deploy/ctl-tool/logging.md, en/includes/deploy/ctl-tool/resource-specific-notes.md
New reusable files document structured logging configuration via LOGS block in toolConfig.json with LOG_LEVEL and LOG_REQUEST_PAYLOADS properties, and comprehensive resource-specific behaviors during configuration export/import including user/group stripping, claim dialect escaping, propagation caveats for user stores and applications, and branding sub-resource naming.
Expand ctl-tool reference documentation
en/includes/deploy/ctl-tool/resource-types-7.x.md, en/includes/deploy/ctl-tool/getting-started-7.x.md
Resource types list expanded to include API Resources, OIDC Scopes, Roles, Email Templates, Governance Connectors, Validation Rules, Organizations, Branding, and conditional entries for SMS/Email Providers, Workflows, and Flows by product and version. Authorization permissions table extended with new Management API scopes and conditional permission rows for templates, actions, senders, and workflows by server version and product.
Embed logging documentation in Identity Server 5.11.0
en/identity-server/5.11.0/docs/setup/promote-configurations.md
Logging section with LOGS configuration example, property reference table, and security warning about exposing credentials when request payload logging is enabled.
Include shared documentation across version-specific guides
en/asgardeo/docs/guides/your-asgardeo/manage-environments/promote-configurations.md, en/identity-server/7.0.0/docs/deploy/promote-configurations.md, en/identity-server/7.1.0/docs/deploy/promote-configurations.md, en/identity-server/7.2.0/docs/deploy/promote-configurations.md, en/identity-server/7.3.0/docs/deploy/promote-configurations.md, en/identity-server/next/docs/deploy/promote-configurations.md
Include directives reference shared logging.md and resource-specific-notes.md files to integrate consistent documentation across all newer version guides.

Suggested labels

Team/Identity Server Core

Suggested reviewers

  • AfraHussaindeen
  • KD23243
🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description includes the purpose and related issue but lacks critical details: test environment and security checks are incomplete, with checkboxes left unchecked and no evidence of testing or security verification. Complete the test environment section and mark or verify the security checks (secure coding standards, FindSecurityBugs plugin run, and secrets verification) before merging.
Title check ❓ Inconclusive The title 'Update ctl tool documentation' is generic and vague, using a broad term that doesn't clearly convey the specific changes made (new resource types, logging configuration, resource-specific notes). Consider a more specific title like 'Add logging and resource-specific documentation for CTL tool' to better reflect the key documentation additions.
✅ 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.

✏️ 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.

Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🧹 Nitpick comments (2)
en/includes/deploy/ctl-tool/logging.md (1)

23-23: 💤 Low value

Consider using active voice in the property description.

The description "are logged" uses passive voice. As per coding guidelines, prefer active voice. Consider rewording to "logs HTTP request bodies" for clarity and directness.

♻️ Suggested revision
-| `LOG_REQUEST_PAYLOADS` | `true`, `false`                  | `false` | When set to `true`, HTTP request bodies are logged at `DEBUG` level for POST and PUT requests. |
+| `LOG_REQUEST_PAYLOADS` | `true`, `false`                  | `false` | When set to `true`, logs HTTP request bodies at `DEBUG` level for POST and PUT requests. |
🤖 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/includes/deploy/ctl-tool/logging.md` at line 23, Update the description
for the LOG_REQUEST_PAYLOADS property to use active voice: replace "HTTP request
bodies are logged at `DEBUG` level for POST and PUT requests" with an active
phrasing such as "logs HTTP request bodies at `DEBUG` level for POST and PUT
requests" while preserving the flag name LOG_REQUEST_PAYLOADS and the behavior
details (DEBUG level, POST and PUT).
en/includes/deploy/ctl-tool/resource-specific-notes.md (1)

3-3: 💤 Low value

Simplify wordy phrase per coding guidelines.

The phrase "to be aware of when using" is verbose. As per coding guidelines, use concise language. Consider "to note when using" or simply "when using".

♻️ Suggested revision
-The following notes describe resource-type-specific behavior to be aware of when using IAM-CTL.
+The following notes describe resource-type-specific behavior when using IAM-CTL.
🤖 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/includes/deploy/ctl-tool/resource-specific-notes.md` at line 3, Replace
the verbose phrase "to be aware of when using" in the document with a concise
alternative such as "to note when using" or simply "when using"; locate the
sentence that currently reads "The following notes describe
resource-type-specific behavior to be aware of when using IAM-CTL." and update
it to "The following notes describe resource-type-specific behavior to note when
using IAM-CTL." (or "when using IAM-CTL") to comply with the concise wording
guideline.
🤖 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/identity-server/5.11.0/docs/setup/promote-configurations.md`:
- Line 168: Replace the bold inline heading "**toolConfig.json**" with the
tab-style include label === "toolConfig.json" and ensure the following JSON
sample is written as a code block using the tab syntax: add a blank line after
=== "toolConfig.json" and start the JSON block with ```json while indenting the
JSON content by 4 spaces (so the code block content is tab-syntax compliant);
locate the literal "**toolConfig.json**" in the file to make this change.

---

Nitpick comments:
In `@en/includes/deploy/ctl-tool/logging.md`:
- Line 23: Update the description for the LOG_REQUEST_PAYLOADS property to use
active voice: replace "HTTP request bodies are logged at `DEBUG` level for POST
and PUT requests" with an active phrasing such as "logs HTTP request bodies at
`DEBUG` level for POST and PUT requests" while preserving the flag name
LOG_REQUEST_PAYLOADS and the behavior details (DEBUG level, POST and PUT).

In `@en/includes/deploy/ctl-tool/resource-specific-notes.md`:
- Line 3: Replace the verbose phrase "to be aware of when using" in the document
with a concise alternative such as "to note when using" or simply "when using";
locate the sentence that currently reads "The following notes describe
resource-type-specific behavior to be aware of when using IAM-CTL." and update
it to "The following notes describe resource-type-specific behavior to note when
using IAM-CTL." (or "when using IAM-CTL") to comply with the concise wording
guideline.
🪄 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: Path: .coderabbit.yml

Review profile: CHILL

Plan: Pro

Run ID: 7d1a1490-c6a7-4d6a-99ec-638fe80e4a62

📥 Commits

Reviewing files that changed from the base of the PR and between 8c4c516 and b352331.

📒 Files selected for processing (11)
  • en/asgardeo/docs/guides/your-asgardeo/manage-environments/promote-configurations.md
  • en/identity-server/5.11.0/docs/setup/promote-configurations.md
  • en/identity-server/7.0.0/docs/deploy/promote-configurations.md
  • en/identity-server/7.1.0/docs/deploy/promote-configurations.md
  • en/identity-server/7.2.0/docs/deploy/promote-configurations.md
  • en/identity-server/7.3.0/docs/deploy/promote-configurations.md
  • en/identity-server/next/docs/deploy/promote-configurations.md
  • en/includes/deploy/ctl-tool/getting-started-7.x.md
  • en/includes/deploy/ctl-tool/logging.md
  • en/includes/deploy/ctl-tool/resource-specific-notes.md
  • en/includes/deploy/ctl-tool/resource-types-7.x.md

Comment thread en/identity-server/5.11.0/docs/setup/promote-configurations.md Outdated
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants