-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: store car alongside content on s3 to then move it in a deterministic way to ipfs #5
Conversation
src/utils.ts
Outdated
region: "us-east-1", | ||
credentials: { | ||
accessKeyId, | ||
secretAccessKey, | ||
}, | ||
}); | ||
|
||
const putBucketLifecycleConfiguration = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need the lifecycle configuration here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's just to make sure it's always there. Since this full lifecycle and its whole concept is managed by this specific service it makes sense that it's created here instead of Terraform no?
src/routes/data/ipfs.ts
Outdated
notes: "Stores JSON data on S3. The data has to have previously been stored on S3 in a format that the service can understand and the caller must be explicitly authorized to call this endpoint.", | ||
description: "Replicates limbo data to IPFS.", | ||
notes: | ||
"Replicated limbo data to IPFS. The data has to be already existing and " + |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Small typo here Replicated
.
No description provided.