-
-
Notifications
You must be signed in to change notification settings - Fork 401
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request: config:set global #955
Comments
@tylerssn What is the difference between?
and
|
My understanding is that |
If only need the "global" value, you can set the scope-id to zero. That's the default. |
Right, but this does not update the store and website scope. Here is my use case: When deploying a dev environment, I do not want to disable my cron but I do want to disable specific cron enable/disable settings. I'm providing JSON in the format of:
This is then parsed in a foreach when deploying my dev environment: Let's say I have these Magento configuration settings: Store Specific Cron Jobs:
If I run This is what I do not want:
If I run
OR
|
@tylerssn ok, Now i know what you are meaning. The name "global" was a little bit misleading for me. The term "global scope" also exists. The feature is more a "set a value in global scope and delete all store-view values". |
@cmuench - I am sure M1 babysitting is not at the top of our Magerun to-do list, however, do you plan on taking any action to ensure inheritance works on set values? At the moment if I |
@tylerson You are right. In the last year the count of M1 Projects at netz98 decreased dramatically. Most of our projects are M2. |
It would be nice to update all values for a setting, regardless of scope.
Something like: magerun config:set path/to/setting value --global
The text was updated successfully, but these errors were encountered: