Coming from Magento 2 On-Prem (self-hosted), we often miss out product attributes bulk update consumers under the .magento.env.yaml file. 

The On-Prem projects normally have these under cronjob and a different setup may not be necessary. However due to how Magento Commerce Cloud infrastructure is built to be, consumers configurations are needed for Queues to run. This is part of the CI/CD structure that is implemented during each deployment (ie. git push).

There are several other consumers that a Magento Cloud project will normally need.
Here’s a default basic of what we will normally run on a basic Cloud setup. More configurations are usually added more as the project goes, but this setup will allow basic features to be enabled.

.magento.env.yaml

stage:
  global:
    SCD_ON_DEMAND: true

  build:
    VERBOSE_COMMANDS: "-vvv"

  deploy:
    VERBOSE_COMMANDS: "-vvv"
    CRON_CONSUMERS_RUNNER:
        cron_run: true
        max_messages: 1000
        consumers:
            - exportProcessor
            - codegeneratorProcessor
            - product_action_attribute.update
            - product_action_attribute.website.update

Some explanations of what the 4 different consumers do

 

– exportProcessor
This will run export queue of CSV export (eg. Catalogs, Customers), and are mainly used for when we are importing/exporting data for upload or comparison.
System > Data Transfer > Export

 

– codegeneratorProcessor
This will run Cart Rules promotion codes generation (possibly gift cards too), otherwise the promotion codes will not be generated if you are needing to generate unique codes. 
Marketing > Promotions > Cart Price Rules > Manage Coupon Codes

 

– product_action_attribute.update
– product_action_attribute.website.update
Both of these will be required when Mass Update is used. Mass Update is an useful action when you have a big chunk of same content you need to update across many different products. For example, Promotion Label or Shipping Type.
Catalog > Inventory > Products > Actions (eg. Update attributes)

 

Let’s also aim to talk about what other configurations are there in some upcoming posts.
This yaml file has a ton of things that we can use to manipulate how our Magento projects can run under the Cloud’s infrastructure.

Do you have more questions or need more help in terms of product attributes bulk update? Do leave a comment down below!

1 thought on “Product Attributes Bulk Update – Magento Commerce Cloud

Comments are closed.