Hi guys. The Consumers module and core idea is super great and makes a lot of sense in the headless Drupal world, so many thanks for doing it (finally we've got image styles exposed, right!?).
The only issue which isn't clear for me is why do we store consumers as content. From DX point of view, it is expected to create a new consumer locally, assign necessary meta data (image styles, etc) and have this consumer exported / imported along with other site configs. It feels pretty similar to configs of Search API module for instance, or any others: once it's configured on a local environment it is expected to be deployed and never touched on the production site.
I might have misunderstood a concept behind the module, however, if consumers are not expected to be modified by a client on the production site (which is not the case, I suppose), then it doesn't seem obvious why it should be a content. Especially considering that it brings additional effort with consumers migration between the environments.
Cheers,
Spleshka.
Closed: works as designed
1.0
Miscellaneous
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
@e0ipso or anyone else: Do you have a suggestion how to handle a setup where we have an otap setup, and don't want production consumers on accept and vice versa (A test application should never have a access to a production environment). We often need to copy back databases to acceptance to have a proper acceptance environment for our customers/clients, so they can test properly.
Any suggestions how to handle this are more than welcome.