Manas-Dikshit opened a new pull request, #34836: URL: https://github.com/apache/shardingsphere/pull/34836
This PR implements Cloud Native Buildpacks for the ShardingSphere Agent to provide a more convenient and standardized way to package and distribute the agent as a container image. This improvement eliminates the need for manually writing a Dockerfile, aligning with modern cloud-native best practices. Changes Implemented: ✅ Added Cloud Native Buildpacks (CNB) support for ShardingSphere Agent. ✅ Updated pom.xml to integrate Buildpacks-based image creation, ensuring seamless Spring Boot compatibility. ✅ Fixed incorrect path issues in Dockerfile and optimized agent deployment. ✅ Improved the Docker image-building process to avoid requiring JAR files in Git repositories. ✅ Ensured compatibility with air-gapped environments by supporting external metadata handling tools. Why This is Needed: The previous method required a manual Dockerfile, which is inconvenient for developers. Cloud Native Buildpacks provide a standardized way to package Java applications for containers. This approach is already used in Apache SkyWalking and aligns with best practices in the Spring Boot ecosystem. References: Related issue: [#32947](https://github.com/apache/shardingsphere/issues/32947) Previous discussion: [#32777](https://github.com/apache/shardingsphere/issues/32777) Similar implementation: [Apache SkyWalking Buildpacks](https://github.com/paketo-buildpacks/apache-skywalking) Testing & Verification: Successfully built and tested the new image using Buildpacks. Verified that the updated pom.xml correctly integrates with the Buildpack workflow. Ensured the Docker image runs as expected without requiring a separate Dockerfile. Next Steps: Review and merge this PR to make ShardingSphere Agent distribution more efficient and developer-friendly. Future enhancements could include CI/CD integration with Buildpacks-based image publishing. -- 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]
