Skip to content
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

app:config:dump locks every configuration setting no alternative to dump specific setting only #11396

Closed
gulshan-streammarket opened this issue Oct 12, 2017 · 4 comments
Assignees
Labels
feature request Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed

Comments

@gulshan-streammarket
Copy link

While using pipeline deployment app:config:dump locks every configuration setting and if merchant want to update any email he must have to run app:config:set command which is not possible. There should be some alternative to dump only specific setting that is required to prepare static content on build system.

Preconditions

  1. Magento 2.2
  2. Pipeline deployment

Steps to reproduce

  1. Run app:config:dump

Expected result

  1. Email/Payment settings(update/enable/disable) must be editable in admin.

Actual result

  1. Settings locked and there is no alternative of app:config:dump

I am not sure whether it is a bug or feature request. But it is not possible piepline deployment with locked confiuratiion. I found Magento-cloud have an alternative command. Am i missing something that i need be aware of.

@magento-engcom-team magento-engcom-team added Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed labels Oct 12, 2017
@magento-engcom-team
Copy link
Contributor

@gulshan-streammarket Thank you for your submission. We recently made some changes to the way we process GitHub submissions to more quickly identify and respond to core code issues. Feature Requests and Improvements should now be submitted to the new Magento 2 Feature Requests and Improvements forum (see details here).

@jalogut
Copy link
Contributor

jalogut commented Nov 25, 2017

This PR will fixes this issue:

Until the PR gets merged, see here a temporal solution to avoid dumping all config settings:

@magento-engcom-team
Copy link
Contributor

Hi @gulshan-streammarket. Thank you for your report.
The issue has been fixed in #12410 by @jalogut in 2.2-develop branch
Related commit(s):

The fix will be available with the upcoming 2.2.5 release.

@VladimirZaets
Copy link
Contributor

Hi @gulshan-streammarket. Thank you for your report.
The issue has been fixed in #14807 by @ihor-sviziev in 2.3-develop branch
Related commit(s):

The fix will be available with the upcoming 2.3.0 release.

@VladimirZaets VladimirZaets added the Fixed in 2.3.x The issue has been fixed in 2.3 release line label May 4, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Fixed in 2.2.x The issue has been fixed in 2.2 release line Fixed in 2.3.x The issue has been fixed in 2.3 release line Issue: Clear Description Gate 2 Passed. Manual verification of the issue description passed Issue: Format is valid Gate 1 Passed. Automatic verification of issue format passed
Projects
None yet
Development

No branches or pull requests

4 participants