verdaccio-aws-s3-storage plugin doesn't work with verdaccio v5.x.x #5061
Unanswered
kgeipel-retail7
asked this question in
Q&A
Replies: 1 comment
-
Addition: we re-tested with the new release version v5.32.1 and still have the same issue. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We try to upgrade our current verdaccio setup from v4.6.1 to v5.31.1, but there is currently an issue with the verdaccio-aws-s3-storage plugin (v10.4.0) that no new artifacts can be written to S3. Everything worked without any problems in the v4.6.1 so it shouldn't be a config issue.
Interesting is, the artifacts are written to the S3 Bucket, but verdaccio returns a HTTP 401, we verified this with a completely new instance with an empty bucket.
Seems that the new verdaccio version somehow is not compatible with the verdaccio-aws-s3-storage plugin v10.4.0.
Also missleading is that the Readme (https://www.npmjs.com/package/verdaccio-aws-s3-storage?activeTab=readme) says that this pluging is compatible with verdaccio v3.x.x and v4.x.x
On the other hand tells the verdaccio v5.x.x docu, that this plugin should be used for storage (maintained by Verdaccio core team), this is kinda misleading.
Can someone tell if this plugin is still officially supported, and if not, what would be the alternative?
Maybe there is a connection to #3699
Beta Was this translation helpful? Give feedback.
All reactions