- Issue created by @bisonbleu
- ๐จ๐ฆCanada bisonbleu
Attaching the
eca.eca.*.yml
as per your instructions.
Let me know if you need this to be done differently. - ๐ฉ๐ชGermany jurgenhaas Gottmadingen
Thank you @bisonbleu this is now published at https://packagist.org/packages/drupal-eca-recipe/eca_lib_0035
What I realized is that the improved dependency management that we have in ECA 3.0 takes it a bit too far in this example. My assumption is that the role "content editor" has some permissions, and those get preserved by the recipe. In addition to that, some of the permissions have dependencies themselves as well, which is why we get the page node type and other config entities contained in the recipe as well.
We may want to look into this separately at some point. For now, I think what's happening is technically correct and determined by config management from Drupal core. But for shareable recipes we may probably change the used roles to something that comes with fewer (or even no) permissions.
- ๐จ๐ฆCanada bisonbleu
Yeahโฆ I wondered why
node.type.article.yml
,node.type.page.yml
andtaxonomy.vocabulary.tags.yml
were included in the recipe. I'll keep your comments in mind if I share more recipes.