Skip to content

feat: Add GCP cost analysis and refine Bicep deployment

Edouard Legoupil requested to merge feat-add-gcp-costs-and-refine-bicep into main_dev

Created by: Edouard-Legoupil

This commit introduces a detailed cost analysis for deploying the application on Google Cloud Platform and refines the Azure Bicep deployment to be more complete and secure.

Key changes include:

  • GCP Cost Analysis: The doc_cloud-deployment.md file has been updated to include a comprehensive cost analysis for GCP, mirroring the structure of the existing Azure analysis. This includes four distinct usage scenarios and a "Cost Per Proposal" metric.

  • Bicep Refinements:

    • The openai.bicep module has been updated to specify a more recent GPT-4 model version.
    • The container_apps.bicep and main.bicep files have been updated to include all necessary environment variables for the Serper API and Entra SSO, which are passed securely as secrets.

  • CI/CD Pipeline Fix: The .github/workflows/deploy.yml file has been corrected to pass all the required secret parameters to the Bicep deployment, ensuring the pipeline is functional.

  • Documentation Updates: The infrastructure/README.md has been updated to reflect the new parameters required for manual deployment.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports