Refactor upgrade detection and maintenance tasks #4127
Merged
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.
There needs to be a process for detecting when a full upgrade is necessary versus only a db upgrade. The current db:status check is not adequate for detecting when maintenance is needed and in the future to detect when a full upgrade may be necessary.
Currently there does not seem a way to properly detect the need for a full upgrade. For example, changes in RabbitMQ configuration will require a full upgrade and thus the current process does not detect that and deployment failures occur. Magento has not released a way to detect this yet and it is in progress here: magento/magento2#39698
This change will allow for easier maintenance by developers now and in the future when we need to add additional conditions for detecting the need for full upgrades and not only partial db upgrades.
Bug fix #…?
New feature?
BC breaks?
Tests added?
Docs added?