Fwd: Update: GIG Service backend Migration form Azure to Choreo

4 views
Skip to first unread message

Malith Jayasinghe

unread,
Oct 7, 2024, 10:14:15 AM10/7/24
to LDF Dev, Visal Vitharana (Intern)


---------- Forwarded message ---------
From: Visal Vitharana (Intern) <vi...@wso2.com>
Date: Wed, Sep 25, 2024 at 9:46 AM
Subject: Update: GIG Service backend Migration form Azure to Choreo
To: <mal...@datafoundation.lk>


Hi all,

This email provides a summary of the changes made as part of migrating the backend of the gig service from Azure to Choreo. These changes have been integrated into the system.

Purpose:
The primary reason for this migration was to address cost issues associated with Azure. Moving to Choreo provides a more cost-effective deployment solution while maintaining the same level of functionality.

Changes Implemented:

  1. Component Configuration:
    Added the necessary configurations to enable the backend service deployment on Choreo.

  2. Security Enhancements:
    Strengthened security by updating the initialization process to securely handle sensitive information, moving away from direct access and adopting Choreo's best practices (Environment variables).

  3. Dockerfile Adjustments:
    Ensured the Dockerfile follows best practices by:

    • Implementing a non-root user for security.

    • Assigning appropriate permissions to the required paths.

  4. Authentication Fixes:
    Resolved authentication issues that were encountered during the migration process, ensuring the service remains secure and functional in Choreo.

Other than these, we made some additional changes in the deployment process. For a detailed review, please refer to the PR here: Gig Service Migration.

Best regards,

Visal.

--
Visal Vitharana | Intern Software Engineer | WSO2
(m)  +94 76 712 3972      |      (e)  vi...@wso2.com


Reply all
Reply to author
Forward
0 new messages