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
Remove upgrade scripts in favor of autoupgrade process #25794
Remove upgrade scripts in favor of autoupgrade process #25794
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
phpstan issue, lgtm otherwise
I'll move all files to the autoupgrade modules (sync them), and add the migrateSettingsFile if needed |
7ff6c48
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Too many deleted files. I can't accept this
You have a conflict ;)
Rebased 3 days ago, I'll wait for QA notification before rebasing again, and again |
@PierreRambaud Could you rebase before sending it in QA ? Thanks |
As I said above, I'll wait for QA to be available, before rebasing again (already did a lot of time 😅 ) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @PierreRambaud
Maybe just indicate in the BC break description, that PrestaShop can no longer self-upgrade, especially with the CLI script which is documented here https://devdocs.prestashop.com/1.7/basics/keeping-up-to-date/upgrade/#how-to-upgrade-prestashop
We'll have to indicate this script is no longer available in the doc and invite people to rely on the autoupgrade module (until maybe a more generic and reusable library/repository is proposed)
@@ -27,14 +27,6 @@ | |||
use PrestaShopBundle\Install\Upgrade; | |||
|
|||
$parametersFilepath = __DIR__ . '/parameters.php'; | |||
if (!file_exists($parametersFilepath)) { | |||
// let's check first if there's some old config files which could be migrated | |||
if (Upgrade::migrateSettingsFile() === false) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a question, how is the parameters.php
file generated now? From what I remember it was only created by this method, even if the name doesn't suggest it I believe it was the only code responsible for generating this file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The file is generate in config/bootstrap.php
this one is for old PrestaShop version and should be handle by the auotupgrade module. Not with a dirty check here :p
8f6ae53
BC breaks
The class
PrestaShopBundle\Install\Upgrade
no longer existsThis change is