feat(platform/ci) Set up deploys from dev

[aarushik93]

Background

Automatic deploys from dev branch to dev environment

Changes 🏗️

Set up gha iam account
Set up workload identity pools so we can use an IAM without keys
Set up CI pipeline to build, push docker images to artifact registery
Set up CI pipeline to do a helm upgrade on all services

Testing 🔍

Note

Only for the new autogpt platform, currently in autogpt_platform/

• Create from scratch and execute an agent with at least 3 blocks
• Import an agent from file upload, and confirm it executes correctly
• Upload agent to marketplace
• Import an agent from marketplace and confirm it executes correctly
• Edit an agent from monitor, and confirm it executes correctly

[qodo-merge-pro]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 4 🔵🔵🔵🔵⚪

🧪 No relevant tests

🔒 Security concerns Sensitive information exposure: The GitHub workflow file (.github/workflows/platform-autogpt-deploy.yaml) contains hardcoded values for the project ID and service account email. These should be stored as GitHub secrets and referenced in the workflow, rather than being directly visible in the code. This exposure could potentially be used by malicious actors to target your GCP resources.

⚡ Recommended focus areas for review Security Concern The workflow is using a hardcoded project ID and service account email. These should be stored as secrets instead of being exposed in the workflow file. Error Handling The workflow lacks proper error handling and rollback mechanisms in case of deployment failures. Consider adding steps to handle errors and potentially roll back changes if a deployment fails. Hardcoded Value The attribute_condition is hardcoded to a specific repository owner. This might need to be parameterized or made more flexible for different environments or organizations.

[Swiftyos]

Nice work @aarushik93 Thank you!