magento / magento/community-features

Feature: extra arguments for setup:config:set

Open
#19 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Imagine2018 moved from magento2 Priority: P4
Dominant language
No language data
Stars
46
Forks
14
PR merge metrics
No merged PRs in 30d

Description

### Preconditions
1. Imported Magento 2.2 environment

### Steps to reproduce

1. Import database from production backup
2. Download/copy/sync `app/etc/config.php` from production
3. Set deployment config to your environment using `bin/magento setup:config:set`
4. Run `bin/magento setup:upgrade`
4. Go to your webserver and it'll tell you that the environment is not installed yet.

### Expected result

1. It would be great if one could tell the `setup:config:set` command that the environment is installed.
2. The environment works after these steps

### Actual result

1. The `install` configuration is missing in `app/etc/env.php`
2. I can't use the environment, except by adding the `install` configuration to `app/etc/env.php`

I would really like the following arguments to be added to the `setup:config:set` command:
- `--install Set install date`
- `--mage-mode Set mage mode`

If you agree, I'd gladly make a Pull Request to make this happen!

**Original Report**: https://github.com/magento/magento2/issues/11318 by @tdgroot

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the setup:config:set command and the configuration files app/etc/env.php and app/etc/config.php described in the issue. Check how the command currently writes deployment settings, then verify that the requested --install and --mage-mode arguments produce a usable environment after setup:upgrade.

Written by the indexing model from the issue text.

Assessment

Domain
cli
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.