After installing this module, you can configure at /admin/config/services/acquia-contenthub/configuration
which entity types should be sent to ACH, plus which bundles for each entity type that has bundles.
This is then all stored in acquia_contenthub.entity_config
. Which is "simple configuration". This MUST be converted to configuration entities. Because configuration entities can have dependencies.
The configuration for the node
entity type's article
bundle (if enabled, and assuming only the teaser
view mode is being "published") would then list:
dependencies:
module:
- node
config:
- node.type.article
- core.entity_view_display.node.article.teaser
This ensures site builders cannot remove modules/entity types/entity bundles/other configuration that the Content Hub module is relying on.
(For a clear example of config dependencies see core/profiles/standard/config/install/core.entity_view_display.node.article.teaser.yml
.)
Any entity type for which Content Hub is not enabled would then not have any such config entity.
See #2308745: Remove rest.settings.yml, use rest_resource config entities for an example of an upgrade path from simple config to configuration entities, including test coverage for that upgrade path!
Comments
Comment #2
Wim LeersI alluded to this at #2822033-3: acquia_contenthub.entity_config is not respected by \Drupal\acquia_contenthub\EntityManager::getAllowedEntityTypes().
Comment #3
Wim LeersSee #2308745: Remove rest.settings.yml, use rest_resource config entities for an example of an upgrade path from simple config to configuration entities, including test coverage for that upgrade path!
Comment #4
Wim LeersTo be clear, the simple act of removing a content type (node bundle) or a particular view mode can trigger unknown behavior in this module.
Comment #5
scor CreditAttribution: scor at Acquia commentedFixed in 8.x-1.0.