Module_0 not working due to changes in AWS bucket
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, terraform
- Domain
- cloud, infrastructure
Research direction
Start by reviewing Module_0's main.tf and the aws_s3_bucket_acl resource shown in the issue, then read the linked AWS bucket ACL discussion. Reproduce the deployment with the current AWS behavior and confirm that Module_0 deploys successfully without the obsolete ACL resource.
Written by the indexing model from the issue text.
Description
It seems you no longer can attach ACL to buckets, see: https://github.com/terraform-aws-modules/terraform-aws-s3-bucket/issues/223. I removed the following resource from main.tf and was able to deploy
resource "aws_s3_bucket_acl" "feast_bucket_acl" {
bucket = aws_s3_bucket.feast_bucket.bucket
acl = "private"
}
- Dominant language
- Jupyter Notebook
- Stars
- 104
- Forks
- 57
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from feast-dev/feast-workshop
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
feast-dev/feast-workshop#23 ·
All issues in feast-dev/feast-workshop
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
level/task module/gcp type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
bug needs-triage service/elbv2
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
hashicorp/terraform-provider-aws#50100 · 1 comment ·