Skip to content

Conversation

@sjd78
Copy link
Member

@sjd78 sjd78 commented Jul 29, 2025

Follow-up: #2368

Close gaps on source platform to match what is in the operator for konveyor-0.8:

  • provider list is just: [cloud-foundry]
  • platforms do no have schema defined coordinates

Summary by CodeRabbit

  • New Features

    • Updated the available platform providers to only include "cloud-foundry".
    • Default platform provider is now set to "cloud-foundry".
  • Bug Fixes

    • Adjusted platform provider selection to ensure only the correct provider is shown in the platform form.
  • Chores

    • Temporarily disabled the "Coordinates" tab in the platform detail drawer.

@coderabbitai
Copy link

coderabbitai bot commented Jul 29, 2025

Walkthrough

The changes update how platform providers are managed and displayed in the source platforms UI. The default and available providers are limited to "cloud-foundry", the provider list hook's return type is updated, and the UI disables the "Coordinates" tab. Imports and logic related to JSON schema rendering are removed or commented out.

Changes

Cohort / File(s) Change Summary
Platform Detail Drawer UI Simplification
client/src/app/pages/source-platforms/components/platform-detail-drawer.tsx
Removes imports and disables the "Coordinates" tab and related schema field rendering by commenting out code.
Platform Provider List Hook and Constants
client/src/app/pages/source-platforms/usePlatformProviderList.ts
Changes default and available providers to "cloud-foundry" only; hook now returns { providers: string[] }.
Platform Form Usage Update
client/src/app/pages/source-platforms/components/platform-form/platform-form.tsx
Updates usage of the provider list hook to destructure the providers property from its return value.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~7 minutes

Poem

A single cloud drifts in the sky,
"Cloud-foundry" now, the only guy.
The tabs are trimmed, the fields are neat,
Simpler forms for users to greet.
With every hop, the code grows light—
A rabbit’s joy: clean, clear, and bright!
☁️🐇

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
  • 📝 Generate Docstrings
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Follow-up: konveyor#2368

Close gaps on source platform to match what is in the operator for konveyor-0.8:
  - provider list is just: [cloud-foundry]
  - platforms do no have schema defined coordinates

Signed-off-by: Scott J Dickerson <[email protected]>
@sjd78 sjd78 force-pushed the fixup_source_platforms branch from 9a37ee3 to 703a7a2 Compare July 29, 2025 04:25
@sjd78 sjd78 requested a review from jortel July 29, 2025 04:26
Copy link

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

🧹 Nitpick comments (2)
client/src/app/pages/source-platforms/usePlatformProviderList.ts (1)

3-3: Consider removing unnecessary sort operation.

The .sort() call on a single-element array is unnecessary and could be removed for clarity.

-const PROVIDER_LIST = ["cloud-foundry"].sort();
+const PROVIDER_LIST = ["cloud-foundry"];
client/src/app/pages/source-platforms/components/platform-detail-drawer.tsx (1)

93-104: Consider cleaning up unused TabKey enum value.

The Coordinates tab is properly commented out with a clear TODO note. However, the TabKey.Coordinates enum value at line 30 is now unused and could be removed or commented out for consistency.

 enum TabKey {
   Details = 0,
-  Coordinates,
+  // Coordinates, // TODO: Add this back if Platforms need schema defined coordinates
   Applications,
 }
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d27194c and 703a7a2.

📒 Files selected for processing (3)
  • client/src/app/pages/source-platforms/components/platform-detail-drawer.tsx (3 hunks)
  • client/src/app/pages/source-platforms/components/platform-form/platform-form.tsx (1 hunks)
  • client/src/app/pages/source-platforms/usePlatformProviderList.ts (1 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
client/src/app/pages/source-platforms/components/platform-form/platform-form.tsx (1)
client/src/app/pages/source-platforms/usePlatformProviderList.ts (1)
  • usePlatformProviderList (5-7)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)
  • GitHub Check: build-and-upload-for-global-ci
  • GitHub Check: unit-test
🔇 Additional comments (4)
client/src/app/pages/source-platforms/usePlatformProviderList.ts (2)

1-1: LGTM! Default provider updated to align with operator 0.8.

The change from "AWS" to "cloud-foundry" aligns with the PR objective to restrict providers for konveyor operator version 0.8 compatibility.


5-6: LGTM! Return type change correctly implemented.

The hook now returns an object with a providers property instead of returning the array directly. This change is properly reflected in the consuming components.

client/src/app/pages/source-platforms/components/platform-detail-drawer.tsx (1)

18-18: LGTM! Unused imports removed.

The removal of JSON schema-related imports aligns with disabling the Coordinates tab functionality.

client/src/app/pages/source-platforms/components/platform-form/platform-form.tsx (1)

62-62: LGTM! Correctly updated to match hook's new return signature.

The destructuring properly extracts the providers array from the updated usePlatformProviderList hook return value. This change maintains compatibility with the existing form logic.

@sjd78 sjd78 added this to the v0.8.0 milestone Jul 29, 2025
Copy link
Member

@ibolton336 ibolton336 left a comment

Choose a reason for hiding this comment

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

VISACK

@sjd78 sjd78 merged commit a369fb9 into konveyor:main Jul 29, 2025
12 checks passed
@sjd78 sjd78 deleted the fixup_source_platforms branch July 29, 2025 15:35
sshveta pushed a commit to sshveta/tackle2-ui that referenced this pull request Oct 31, 2025
Follow-up: konveyor#2368

Close gaps on source platform to match what is in the operator for
konveyor-0.8:
  - provider list is just: [cloud-foundry]
  - platforms do no have schema defined coordinates

Signed-off-by: Scott J Dickerson <[email protected]>
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