Chore/add support to open search #46
Merged
+77
−17
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is the goal?
Provide configuration parameters to use opensearch
How is it being implemented?
This pull request includes several changes to support the use of OpenSearch as an alternative to Elasticsearch in the Magento setup. Key changes include modifications to environment configuration, Docker setup, and entrypoint scripts.
Environment Configuration Updates:
.env.sample
to allow configuration for different Magento versions.M2_SEARCH_ENGINE
environment variable to switch between Elasticsearch and OpenSearch. Updated related configurations accordingly.Docker Setup Modifications:
docker-compose.yml
to add a new service definition for OpenSearch, including necessary ports, environment settings, and volume mappings.Script Adjustments:
.docker/magento/m2-entrypoint.sh
to dynamically configure search engine parameters based on the selected search engine. [1] [2]setup.sh
andteardown.sh
to use the appropriate Docker profile based on the configured search engine. [1] [2]Opportunistic refactorings
Conditional Sample Data Installation:
.docker/magento/HelperModule/Sequra/Helper/Console/Setup.php
to skip setup ifM2_SAMPLE_DATA
is not set..env.sample
to includeM2_SAMPLE_DATA
variable with instructions on enabling or disabling sample data installation.How is it tested?
Manual tests
How is it going to be deployed?
Standard deployment