Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 as Storage Backend #25

Merged
merged 19 commits into from
Jun 15, 2024
Merged

S3 as Storage Backend #25

merged 19 commits into from
Jun 15, 2024

Conversation

fullerzz
Copy link
Owner

No description provided.

@fullerzz fullerzz self-assigned this Jun 15, 2024
fullerzz added 18 commits June 15, 2024 15:17
etectContentType when returning downloaded file from s3
* wip: search files by tag

* wip: sqlite for db instead of dynamo

* writes to db on file upload are working

* added db.go with functions to add item to table and list files in table

* getFileMetadata successfully queries sqlite table when file exists. TODO: handle error

* returns 404 if error indicates file wasn't found - else 500

* moved additional table functionality to db.go

* removed more functions in aws.go - TODO: move QueryTags functionality to sqlite table

* moved all db functionality from dynamo to sqlite

* removed dynamo table from iac

* todo: mock s3 and any aws calls in tests

* removed commented-out line of code

* added tfvars to support dev and prod envs

* removed config. will set the values in scalr ui for now
@fullerzz fullerzz force-pushed the 21-use-s3-as-storage-backend branch from d5064d4 to abf9d35 Compare June 15, 2024 22:17
Copy link

scalr bot commented Jun 15, 2024

✅ Scalr runs report (abf9d35)

✅ Scalr runs report

Scalr finished execution of runs in all workspaces that are affected by a commit (abf9d35). The cumulative and per-workspace reports you can find below.

Summary

  • Overall status: Success ✅
  • Runs triggered - 1
  • Successful - 1 (review)

Per-workspace report

Run ID: run-v0odfa6jj52sn11vi
Workspace: picloud
Environment: Dev
Run mode: Plan Only
Status: Success ✅

Duration: 19s

Resources changes

To create: 12
aws_iam_access_key.picloud {
  id: (known after apply)
}

aws_iam_user.picloud {
  id: (known after apply)
  name: picloud
}

aws_iam_user_policy.picloud-s3-policy {
  id: (known after apply)
  name: picloud-s3-policy
}

aws_s3_bucket.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket.picloud-bucket-logs {
  id: (known after apply)
}

aws_s3_bucket_acl.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_acl.picloud-bucket-logs-acl {
  id: (known after apply)
}

aws_s3_bucket_logging.picloud-bucket-logging {
  id: (known after apply)
}

aws_s3_bucket_ownership_controls.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_ownership_controls.picloud-bucket-logs {
  id: (known after apply)
}

aws_s3_bucket_public_access_block.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_server_side_encryption_configuration.picloud-bucket {
  id: (known after apply)
}

Copy link

scalr bot commented Jun 15, 2024

✅ Scalr runs report

Scalr finished execution of runs in all workspaces that are affected by a commit (4ad1656). The cumulative and per-workspace reports you can find below.

Summary

  • Overall status: Success ✅
  • Runs triggered - 1
  • Successful - 1 (review)

Per-workspace report

Run ID: run-v0odfaal2uhhfsequ
Workspace: picloud
Environment: Dev
Run mode: Plan Only
Status: Success ✅

Duration: 27s

Resources changes

To create: 12
aws_iam_access_key.picloud {
  id: (known after apply)
}

aws_iam_user.picloud {
  id: (known after apply)
  name: picloud-dev
}

aws_iam_user_policy.picloud-s3-policy {
  id: (known after apply)
  name: picloud-dev-s3-policy
}

aws_s3_bucket.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket.picloud-bucket-logs {
  id: (known after apply)
}

aws_s3_bucket_acl.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_acl.picloud-bucket-logs-acl {
  id: (known after apply)
}

aws_s3_bucket_logging.picloud-bucket-logging {
  id: (known after apply)
}

aws_s3_bucket_ownership_controls.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_ownership_controls.picloud-bucket-logs {
  id: (known after apply)
}

aws_s3_bucket_public_access_block.picloud-bucket {
  id: (known after apply)
}

aws_s3_bucket_server_side_encryption_configuration.picloud-bucket {
  id: (known after apply)
}

@fullerzz fullerzz merged commit 2d20105 into dev Jun 15, 2024
3 of 4 checks passed
@fullerzz fullerzz deleted the 21-use-s3-as-storage-backend branch June 15, 2024 22:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant