Skip to content

Implement cross-environment object migration #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 3 commits into
base: ee-features
Choose a base branch
from

Conversation

ElierHG
Copy link
Owner

@ElierHG ElierHG commented Aug 17, 2025

Proposed changes

This PR introduces the core functionality for moving actual applications, data queries, and datasources between different environments. Previously, only the metadata of "managed objects" could be transferred; this change enables the deployment of the actual object content.

This addresses the user's need to move objects like apps and data queries between environments.

Types of changes

What types of changes does your code introduce to Lowcoder?
Put an x in the boxes that apply.

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.
Put an x in the boxes that apply.

  • Lint and unit tests pass locally with my changes
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

This feature implements a two-step transfer process: first, the managed object metadata is transferred, and then the actual object (app, query, or datasource) is deployed via new backend endpoints.

Key components introduced/modified:

  • Backend (ObjectDeploymentController.java): New controller with placeholder endpoints for /deploy/app, /deploy/query, and /deploy/datasource. Note: The actual deployment logic within these endpoints is currently marked with TODO comments and needs to be implemented by the maintainers.
  • Frontend (TransferObjectModal.tsx): A new modal component that provides a user interface for selecting the target environment and configuring deployment options (e.g., transfer credentials, publish on target).
  • Frontend Service (managed-objects.service.ts): The transferManagedObject function has been updated to trigger the new backend deployment endpoints after the metadata transfer. A new deployObject function was also added for direct deployment.
  • Documentation (OBJECT-MOVEMENT-README.md): A comprehensive guide explaining the feature, its architecture, usage, and API endpoints.
  • Tests (test-object-deployment.js): A new test script to verify the new backend deployment endpoints.

This PR provides the full UI and API structure for object movement, ready for the core deployment logic to be filled in on the backend.


Open in Cursor Open in Web

Co-authored-by: elierherrera96 <elierherrera96@gmail.com>
Copy link

cursor bot commented Aug 17, 2025

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
Learn more about Cursor Agents

cursoragent and others added 2 commits August 17, 2025 23:03
Co-authored-by: elierherrera96 <elierherrera96@gmail.com>
Co-authored-by: elierherrera96 <elierherrera96@gmail.com>
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