Implement cross-environment object migration #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.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.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:
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 withTODO
comments and needs to be implemented by the maintainers.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).managed-objects.service.ts
): ThetransferManagedObject
function has been updated to trigger the new backend deployment endpoints after the metadata transfer. A newdeployObject
function was also added for direct deployment.OBJECT-MOVEMENT-README.md
): A comprehensive guide explaining the feature, its architecture, usage, and API endpoints.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.