5 ms·

Is it just me or is this missing plain artifacts - those that are not packaged for a specific tool? I'm thinking of plain binaries and resources required for th

Is it just me or is this missing plain artifacts - those that are not packaged for a specific tool? I'm thinking of plain binaries and resources required for things like db build tools and automated testing tools - just files really. How do I publish a tarball up to this, for example? Also the lack of nuget is a major issue.

greyskull 6y ago
I think CodeArtifact loses value when you aren't using a package manager; the benefit is an api-compatible service with various controls and audits built on top. Out of curiosity, what would you want from this service for the "plain binary" use-case when S3 already exists?
- ec109685 6y ago
  It’s nice having the metadata around the push available versus raw blobs to s3.
  - bostik 6y ago
    Objects in S3 can have custom metadata associated with them. Look at the returned data for the HeadObject call.[0] It's not advertised in the documentation, but HeadObject(Bucket, Key)['Metadata'] is a neat dictionary of custom values. 0: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObje...
  - camhart 6y ago
    S3 supports metadata (see https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-object-metadata.html https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-o...). Perhaps I don't understand what you're saying fully though--as I don't fully understand your comment.
  - StreamBright 6y ago
    You mean like Object Metadata for S3? https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadat...
- pskinner 6y ago
  I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http, but I'd like something that's as easy to setup and use as nexus for these files - and something that forces a structure for how they are organised. Stops arguments and people doing whatever they want.
  - StreamBright 6y ago
    >> I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http, This is where S3 really shines. You can give developers access through group membership while servers using instance profiles. We have implemented a fine grained access control for the S3 repos that works really well. Of course you access the content via HTTPS.
    - pskinner 6y ago
      Fair enough, I dislike having the idea of having disparate systems where one type of the same thing is stored on a different system from a second type of the same thing. IAM is on the AWS repo aswell isn't it? I guess it wouldn't be so bad then.
deleted 6y ago
[deleted]

greyskull 6y ago

I think CodeArtifact loses value when you aren't using a package manager; the benefit is an api-compatible service with various controls and audits built on top. Out of curiosity, what would you want from this service for the "plain binary" use-case when S3 already exists?

ec109685 6y ago
It’s nice having the metadata around the push available versus raw blobs to s3.
- bostik 6y ago
  Objects in S3 can have custom metadata associated with them. Look at the returned data for the HeadObject call.[0] It's not advertised in the documentation, but HeadObject(Bucket, Key)['Metadata'] is a neat dictionary of custom values. 0: https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObject.html https://docs.aws.amazon.com/AmazonS3/latest/API/API_HeadObje...
- camhart 6y ago
  S3 supports metadata (see https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-object-metadata.html https://docs.aws.amazon.com/AmazonS3/latest/user-guide/add-o...). Perhaps I don't understand what you're saying fully though--as I don't fully understand your comment.
- StreamBright 6y ago
  You mean like Object Metadata for S3? https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadat...
pskinner 6y ago
I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http, but I'd like something that's as easy to setup and use as nexus for these files - and something that forces a structure for how they are organised. Stops arguments and people doing whatever they want.
- StreamBright 6y ago
  >> I think mainly the ease of having security dealt with around who can access etc really. Ofc you can just upload files and serve them over http, This is where S3 really shines. You can give developers access through group membership while servers using instance profiles. We have implemented a fine grained access control for the S3 repos that works really well. Of course you access the content via HTTPS.
  - pskinner 6y ago
    Fair enough, I dislike having the idea of having disparate systems where one type of the same thing is stored on a different system from a second type of the same thing. IAM is on the AWS repo aswell isn't it? I guess it wouldn't be so bad then.

deleted 6y ago

[deleted]