Closed ddrozdik closed 5 years ago
@hamrant could you please ensure this bug is not exists in your update tool, decoupled to drupal.org?
@ddrozdik is it possible to share more details about
@ddrozdik @Sanchiz @podarok Hey friends, could we please get an update on this? It feels like this should get resolved sooner rather than later. Thanks!
OpenY Upgrade tool is inapropriate at this moment See https://github.com/ymcatwincities/openy/pull/1084 , team Let's go from there
@podarok and 5J are working on this one for a near-term bug-fix release.
Field config_property
from openy_config_upgrade_logs
used for storing last updated property during OpenY update, it's not related to any conflict and only provides information what exactly should have been updated.
Anyway in new openy_upgrade_tool version this field will be removed, so this issue can be closed.
cc @podarok @ddrozdik
After updating openY to the latest version using
openy_upgrade_tool
dashboard I can see a list of conflicts. For example, I have a conflict with the configviews.view.classes_listing
. And I see that conflict with propertydisplay.search_form.cache_metadata.tags
but when I open diff I can see that there are much more conflicts in different places. So using serviceopeny_upgrade_tool.param_updater
I can't resolve conflicts, I have to specify a property for each place where I have a conflict or import the whole config.I guess we should not display a value in the
UPDATE PROPERTY
column on the page at all, or display it for each changed property in a config.