mirror of
https://github.com/ToolJet/ToolJet
synced 2026-05-24 09:28:31 +00:00
|
Some checks are pending
CI / build (push) Waiting to run
CI / lint-for-plugins (push) Blocked by required conditions
CI / lint-for-server (push) Blocked by required conditions
CI / lint-for-frontend (push) Blocked by required conditions
CI / unit-test (push) Blocked by required conditions
CI / e2e-test (push) Blocked by required conditions
aws-actions/configure-aws-credentials@v4 exports AWS_SECRET_ACCESS_KEY (with the AWS_ prefix), but the S3 uploader was reading SECRET_ACCESS_KEY, leaving credentials.secretAccessKey undefined. aws-sdk v2 silently fell back to the default credential provider chain so this typo went unnoticed for years; the aws-sdk v3 migration in #15147 made an explicit credentials object authoritative, so every upload since has failed with "Resolved credential object is not valid" (0/567 files on recent runs). Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| upload-to-s3.js | ||
| upload-to-s3.sh | ||