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

AWS S3 in CAS proxy #269

Closed
3 tasks
migmartri opened this issue Jul 25, 2023 · 2 comments · Fixed by #390
Closed
3 tasks

AWS S3 in CAS proxy #269

migmartri opened this issue Jul 25, 2023 · 2 comments · Fixed by #390
Labels

Comments

@migmartri
Copy link
Member

migmartri commented Jul 25, 2023

The CAS proxy is a layer in front of different CAS backends. At the moment of this writing only OCI repositories are supported.

image

THe goal of this task is to

  • Allow the artifact CAS proxy to be able to support more than 1 provider (OCI, S3) at the same time
  • The specific provider (OCI, S3) could be selected on the fly in each request, so in addition to receiving the credentials reference now it will also receive the backend type.
  • Implement AWS s3 blob storage CAS backend

image

@migmartri migmartri changed the title AWS s3 in CAS proxy AWS S3 in CAS proxy Jul 25, 2023
@danlishka
Copy link
Member

What if we first add support for AWS S3 and then we will tackle a way to have a CAS proxy? Or we need to do both at the same time?

@migmartri
Copy link
Member Author

What if we first add support for AWS S3 and then we will tackle a way to have a CAS proxy? Or we need to do both at the same time?

We discussed this offline and there was a misunderstanding. The scope of this issue is not to change how Chainloop attestation process uses the CAS, but the internal implementation of the cas-proxy. How it could handle requests for different backends.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants