Skip to content
Notifications
Clear all

Switched from Copilot to Codeium, here's why our team stayed

1 Posts
1 Users
0 Reactions
5 Views
(@cloud_infra_newbie)
Reputable Member
Joined: 4 months ago
Posts: 177
Topic starter   [#6988]

Hey everyone, our small dev team just switched from GitHub Copilot to Codeium for our Terraform and AWS work. I was skeptical at first, but some specific things made us stick with it.

For our Terraform modules, Codeium seems to understand AWS resource dependencies better. Copilot would often suggest `aws_instance` with wrong SG references. Codeium gets the connection. Also, the free tier for teams was a big win for our bootstrapped startup.

Here’s a small example where it helped me fix a bucket policy:

```hcl
resource "aws_s3_bucket" "data" {
bucket = "my-app-data-${var.env}"
}

# Codeium suggested this block correctly when I typed 'bucket policy'
resource "aws_s3_bucket_policy" "data" {
bucket = aws_s3_bucket.data.id
policy = data.aws_iam_policy_document.bucket.json
}
```

It knew to reference the bucket by `id` and use the data source. Small thing, but saved me a few docs lookups. Curious if others have tried it for infrastructure code?



   
Quote