Split permissions for product attribute config and value content entities

Created on 11 April 2020, over 4 years ago
Updated 13 March 2024, 9 months ago

A bit of a spiritual follow-up to #2904459: Product attributes edit but not create β†’ - the ProductAttribute config entity and ProductAttributeValue content entity share a single admin permission, administer commerce_product_attribute. This results in users (e.g., content moderators/editors) making updates to the config entity such as changing an attribute name, which when using a deployment strategy that imports config (e.g., assumes config changes will be made in dev and pushed to production) these changes will be overwritten.

I think it would be sensible to split these permissions (or at least dynamically support such a differentiation) to avoid a WTF condition on the part of developers and non-technical end users.

πŸ“Œ Task
Status

Active

Version

2.0

Component

Product

Created by

πŸ‡ΊπŸ‡ΈUnited States bradjones1 Digital Nomad Life

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

Merge Requests

Comments & Activities

Not all content is available!

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

Production build 0.71.5 2024