-
Notifications
You must be signed in to change notification settings - Fork 978
feat: implement S3 integration for storing and retrieving digest files #427
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
Conversation
0c9ef62 to
f94bbf9
Compare
ix-56h
left a comment
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.
The changes to the ingestion api endpoint are wrong, if you need help correcting them, i can do it for you !
46e5acb to
10ef67d
Compare
46b40ea to
85ff2ce
Compare
3361419 to
aa21a74
Compare
|
⚙️ Preview environment was undeployed. |
e8a23bf to
416254c
Compare
still not working in PR env with aws s3
NicolasIRAGNE
left a comment
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.
A few points
- S3_DIRECTORY_PREFIX is ignored when retrieving
- the ingest file name should be user-repo.txt (like we have today) i think
- when we do
# Extract source from URL or default to "unknown"
git_source = {
"github.com": "github",
"gitlab.com": "gitlab",
"bitbucket.org": "bitbucket",
}.get(hostname, "unknown")
can't we just do raw hostname/... ? eg /github.com/blablabla
kinda like what golang does
596eb7c to
c022cfb
Compare
|
LGTM |
Closes https://github.com/coderamp-labs/issue-board/issues/13