chore(migration): merge Construct-X portal-assets customizations into Tractus-X fork baseline - #514
Open
devajipatil wants to merge 6 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR migrates the existing Construct-X customizations from the legacy portal-assets-old repository into the newly created fork of the Tractus-X portal-assets repository.
Background:
The previous Construct-X assets repository was not created as a GitHub fork, which limited the ability to synchronize with upstream Tractus-X changes. A fresh fork has now been created, and this PR merges the downstream Construct-X branch feature/construct-x-assets onto the upstream baseline.
Scope:
Merge legacy Construct-X assets service changes into fork main
Preserve existing Construct-X configurations and behavior
Align repository history with Tractus-X upstream to enable future upstream updates
Impact / Risk:
Large diff expected due to unrelated history merge
No intentional functional changes beyond migration
Requires validation of asset upload, listing, deletion, and contract-related flows after deployment
Validation Plan:
Ensure CI build succeeds from fork repository
Deploy updated service to staging environment
Verify asset lifecycle operations and integration with portal frontend
Follow-up:
Future updates from Tractus-X upstream can be synchronized using standard fork update workflows