fix: change factory-reset functions to delete named volume for opensearch-data

[lucaseduoli]

This pull request removes support for configuring the OpenSearch data path via environment variables and local directories, fully transitioning OpenSearch data persistence to Docker-managed named volumes. This simplifies configuration and data management, making the system more robust and less error-prone. All related documentation, configuration fields, and code paths for the old directory-based approach have been removed or updated.

Configuration and Environment Variable Cleanup:

• Removed OPENSEARCH_DATA_PATH from .env.example, the EnvManager, and all related config fields, so OpenSearch data is no longer configurable via environment variables or local paths. [1] [2] [3] [4] [5]

Makefile and Data Reset Updates:

• Updated the factory-reset and clear-os-data Makefile targets to remove references to the opensearch-data directory and clarify that OpenSearch data is now managed as a Docker volume. [1] [2] [3]

Script and Container Manager Refactor:

• Refactored scripts/clear_opensearch_data.py and ContainerManager.clear_opensearch_data_volume() to operate on Docker volumes instead of directories, including logic to handle different possible volume names. [1] [2]

Miscellaneous:

• Adjusted logic for inserting the OPENRAG_VERSION line in .env files to account for the removal of OPENSEARCH_DATA_PATH.

[zzzming]

Please do not remove existing env variable. We have other provisioning components depending on it.

[lucaseduoli]

@zzzming that env variable was not used, because it does not alter the behavior of the opensearch image. It was an env variable that was exclusive to docker-compose.yml

[mpawlow]

@lucaseduoli

Code Review 1

• See PR comments: (a) to (f)

[github-actions]

Build successful! ✅
Deploying docs draft.
Deploy successful! View draft