Hi,

Im having some problems with products attributes and configuration management.
I've given permission to my client to manage product attributes. But, since its a configuration, every time I make a deploy the configuration import will override the relation between the variation and the attribute.

Let me try to exemple:

I have two product attributes in configuration files, if my client creates another one it works, but when I try to import a configuration change on the variation type it removes the attribute reference from the variation, removing the variation field from the product create page.

The attribute is still there, its checked as if the relation was there, but it does not show in the variation form. If the attribute has no data, I can uncheck and check and the form field is back. But when it has data it gets disabled.

What I can see as possible solutions to my problem:

#1 - Let my client only edit product attributes, but not create or link with variation. But I could no found any permission for that, the only permission available gives full control over attributes.

#2 - Force the relation to exist after a config import. Check if the attribute is related to variation and force that on variation too. But could not find anyway to do that either

Anything im seeing wrong? Do you guys know a better solution to this?

Comments

diogoviannaaraujo created an issue. See original summary.

czigor’s picture

Status: Active » Closed (works as designed)

This is not commerce-specific but a general a configuration management workflow issue. There are several ways to address this. One way would be to always export the live site config before deployment and commit it to git. For other ways I can recommend the slides of bircher, e.g. https://events.drupal.org/vienna2017/sessions/advanced-configuration-man....