Add workflow to deploy to AKS

[zepor]

Add workflow to deploy to AKS

[codeautopilot[bot]]

PR summary

The Pull Request introduces a new GitHub Actions workflow named fedeploy that automates the deployment of a containerized application to Azure Kubernetes Service (AKS). The workflow triggers on pushes to the main branch or can be manually dispatched. It consists of two jobs: buildImage and deploy.

The buildImage job logs into Azure, builds a Docker image from a Docker Compose file, and pushes it to Azure Container Registry (ACR) using the commit SHA as the image tag.

The deploy job, which depends on buildImage, also logs into Azure, sets up Kubernetes context for the AKS cluster, and uses Helm to deploy the application to AKS with overrides specified for the container image repository and tag.

Suggestion

• Ensure that the secrets (AZURE_CLIENT_ID, AZURE_SUBSCRIPTION_ID, AZURE_TENANT_ID) are properly set in the GitHub repository for Azure login.
• Verify that the Helm chart path and override values are correctly configured for the deployment.
• Consider adding error handling or rollback strategies in case the deployment fails.
• It might be beneficial to include a step to run tests before the deployment to ensure that the new changes are stable.
• Check if the admin flag for AKS context should be set to true or false depending on the required access level for the deployment.
• Ensure that the Docker Compose file path (./docker-compose.prod.yml) and the context path (./frontend-container) are correct.
• Validate that the Helm upgrade command includes all necessary flags and parameters for a successful deployment.

_Disclaimer: This comment was entirely generated using AI. Be aware that the information provided may be incorrect._ Current plan usage: 37.33% **Have feedback or need help?** [Discord](https://discord.gg/r72ykfvyx7) [Documentation](https://docs.codeautopilot.com/) [support@codeautopilot.com](mailto:support@codeautopilot.com)