Skip to content
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

Direct migration from 3.x to 4.3.0 and onwards #3495

Open
BLasan opened this issue Jan 6, 2025 · 2 comments
Open

Direct migration from 3.x to 4.3.0 and onwards #3495

BLasan opened this issue Jan 6, 2025 · 2 comments
Assignees

Comments

@BLasan
Copy link

BLasan commented Jan 6, 2025

Current Limitation

Currently, there's no automated way to migrate apim from 3.2.0 to 4.3.0 (and higher). After migrating to 4.2.0, 4.2.0 to 4.3.0 migration scripts need to be run manually.

Suggested Improvement

Automate the apim 3.2.0 to 4.3.0 (and higher) migration

Version

No response

@BLasan
Copy link
Author

BLasan commented Jan 8, 2025

[Update 07/01/2025]

  • Implemented the V430Migration class for the migration client tool in order to automate the 4.3.0 migration from 3.2.0.
  • Added the relevant sql files into the pre-migration-scripts which will be executed during the migration process.

@BLasan
Copy link
Author

BLasan commented Jan 8, 2025

[Update 08/01/2025]

  • Started testing the tool on 4.2.0 migration. Working on the data population for apim 3.2.0 and found some issues with the jmeter scripts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant