Issue #SBCOSS-00: Create Github actions to publish docker image to GHCR

[chethann007]

Create GitHub Actions workflow to publish Keycloak Docker image to GHCR

Description

This PR introduces a new GitHub Actions workflow in the sunbird-auth repository to automate the build and publishing of the Keycloak Docker image to GitHub Container Registry (GHCR).

Background

Previously, the Keycloak image was built from the sunbird-ed-installer repository, requiring manual steps to build the JAR from sunbird-auth and copy it into the installer before building the image. This process was error-prone and time-consuming.

Changes in this PR

• Moved necessary files for building the Keycloak image from sunbird-ed-installer to the sunbird-auth repository.
• Created a GitHub Actions workflow triggered on tag pushes (on: push: tags: '*').
• Set up the build environment using JDK 11 and Maven caching.
• Automated the process of building the JAR, copying it into the Keycloak provider directory, and building the Docker image.
• Pushed the image to GHCR with a structured naming convention including the tag, commit SHA, and run number.

Benefits

• Removes manual steps, improving developer efficiency.
• Ensures consistent, reproducible builds.
• Integrates image publishing into the CI/CD pipeline for faster deployments.

Description by Korbit AI

What change is being made?

Create a GitHub Actions workflow to build and publish a Keycloak Docker image to the GitHub Container Registry (GHCR).

Why are these changes being made?

This change automates the process of building and deploying the Keycloak Docker image, ensuring a streamlined and consistent deployment workflow for the Sunbird Keycloak setup project whenever a new tag is pushed to the repository. It enhances the containerization strategy by employing a CI/CD pipeline that supports efficient integration and delivery, optimizing for future scalability and maintainability.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[korbit-ai]

Korbit doesn't automatically review large (3000+ lines changed) pull requests such as this one. If you want me to review anyway, use /korbit-review.