magento / magento/magento2

Magento 2.4.0 Missing Elastic Search options in setup:config:set

Open
#29,338 16 comments 6 reactions 1 assignee View on GitHub

@lbajsarowicz is already working on this.

Since Aug 30, 2026.

Area: Catalog Component: Config Issue: Confirmed Priority: P3 Reported on 2.4.0 Reproduced on 2.4.x
Dominant language
PHP
Stars
12.2k
Forks
9.4k
PR merge metrics
No merged PRs in 30d

Description

### Preconditions (*)

1. Magento 2.4.0, 2.4-develop
2. PHP 7.4.8
3. MySQL 8.0.21

### Steps to reproduce (*)

1. Setup vanila Magento
2. Run `bin/magento setup:config:set --help | grep elastic`
3. No options related to Elastic Search

### Expected result (*)

1. Command should contain Elastic Search options like:
--search-engine
--elasticsearch-host
--elasticsearch-port
--elasticsearch-index-prefix
--elasticsearch-timeout
--elasticsearch-enable-auth
--elasticsearch-username
--elasticsearch-password
2. Elastic Search is mandatory so should be present in setup:config:set

### Actual result (*)

1. Elastic Search options are absent
2. Possible to set it up via setup:install command, however when you work on installed Magento you have to change ES setting via Admin or System Config / ENVs etc.
---
Please provide [Severity](https://devdocs.magento.com/guides/v2.3/contributor-guide/contributing.html#backlog) assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

- [ ] Severity: **S0** _- Affects critical data or functionality and leaves users without workaround._
- [x] Severity: **S1** _- Affects critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S2** _- Affects non-critical data or functionality and forces users to employ a workaround._
- [ ] Severity: **S3** _- Affects non-critical data or functionality and does not force users to employ a workaround._
- [ ] Severity: **S4** _- Affects aesthetics, professional look and feel, “quality” or “usability”._

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.