Ma77Ball opened a new pull request, #5672: URL: https://github.com/apache/texera/pull/5672
### What changes were proposed in this PR? - Moved 6 config objects (`ApplicationConfig`, `StorageConfig`, `UdfConfig`, `PekkoConfig`, `EnvironmentalVariable`, `PythonUtils`) from `common/config/.../org/apache/texera/amber/config/` into `.../org/apache/texera/config/`, changing their package from `org.apache.texera.amber.config` to `org.apache.texera.config` so they sit alongside the config objects already there (`AuthConfig`, `GuiConfig`, `UserSystemConfig`, etc.). - Rewrote all 53 import sites across the repo to the new package, so non-engine modules (`config-service`, `computing-unit-managing-service`, `workflow-compiling-service`, and others) no longer import an `amber`-named package for config that lives in `common/config`. - Merged the now-duplicate same-package import lines in `ConfigService` and `ComputingUnitManagingResource`. - Pure rename and import rewrite, no behavior change. `org.apache.texera.amber.util` (a separate, multi-module package) is intentionally left out of scope. ### Any related issues, documentation, discussions? Closes: #5668 ### How was this PR tested? - Run `sbt "Config/compile" "ConfigService/compile" "ComputingUnitManagingService/compile" "WorkflowCompilingService/compile" "AccessControlService/compile" "FileService/compile" "WorkflowCore/compile" "WorkflowOperator/compile"` and expect every module to report `[success]`. - The `amber` module fails to compile on a pre-existing jOOQ codegen gap (`VIRTUAL_ENVIRONMENTS` in `PveManager.scala`) that reproduces on a clean `main` without this change, so it is unrelated to the rename; confirm `amber` compiles green in CI where full jOOQ codegen runs, and check that no `org.apache.texera.config` import in `amber` fails to resolve. - No behavior changed, so existing test suites should pass unchanged; the rename only affects package and import paths. ### Was this PR authored or co-authored using generative AI tooling? Co-authored with Claude Opus 4.8 in compliance with ASF -- 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]
