bobbai00 opened a new pull request, #3892: URL: https://github.com/apache/texera/pull/3892
Closes #3891 ## Summary This PR restructures the `bin/deployment/` directory and updates all Dockerfiles to be compatible with the recent repository changes where `core` was renamed to `common` and services were moved to the root level. ## Changes Made ### Directory Restructuring - Moved all contents from `bin/deployment/` directly to `bin/` - Moved `bin/deployment/k8s/texera-helmchart/` to `bin/k8s/` (renamed from texera-helmchart) - Removed the now-empty `deployment` folder ### Dockerfile Updates Updated all Dockerfiles to work with build context set at project root: - **Microservices** (`file-service`, `access-control-service`, `config-service`, `workflow-compiling-service`, `workflow-computing-unit-managing-service`): Each now copies only `common/` and their specific service folder - **Main application** (`texera-web-application`): Copies `common/`, `amber/`, and `frontend/` - **Computing units** (`computing-unit-master`, `computing-unit-worker`): Copy `common/` and `amber/` - Updated all COPY paths from `core/` to `common/` - Changed working directory from `/core` to `/texera` - Added explicit `project/` and `build.sbt` copy for clarity ### Symlink Fixes - Updated symlinks in `bin/k8s/files/` to point to `../../../sql/` instead of `../../../../core/scripts/sql/` - All SQL file symlinks now resolve correctly ### Build Scripts - Build scripts (`build-images.sh`, `merge-image-tags.sh`) already used correct relative paths and work without modification ## Test Plan All Docker images can now be built successfully from project root: ```bash docker build -f bin/texera-web-application.dockerfile -t texera/texera-web-application:test . docker build -f bin/file-service.dockerfile -t texera/file-service:test . # ... and so on for all services ``` 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
