DISABLE_AUTO_UPDATE flag lost if the entity is imported as dependency

Created on 5 December 2020, about 4 years ago
Updated 26 February 2023, almost 2 years ago

Problem/Motivation

I have changed the status of a config entity in the import tracking table to 'DISABLE_AUTO_UPDATE', which I expect this entity will be skipped for future updates. However, it seems upon the next import, the status is changed back to 'imported' again.

Steps to reproduce

Mark a dependent config entity as 'disable_auto_update' in the import_tracking table, then import the parent entity.

Proposed resolution

Fix the bug.

🐛 Bug report
Status

Needs work

Version

2.0

Component

Code

Created by

🇨🇳China weynhamz Ningbo

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇨🇦Canada scor Toronto

    Instead of using custom code and direct DB access to modify the tracking table, if you can provide steps to reproduce the issue using the acquia_contenthub_unsubscribe module, it will be a more compelling case to get this fixed.

Production build 0.71.5 2024