ci: fix plonds s3 probe and signing fallback

This commit is contained in:
lincube
2026-04-21 00:11:17 +08:00
parent a31ae3cd58
commit 82f1e77393

View File

@@ -724,6 +724,7 @@ jobs:
S3_REGION: ${{ vars.S3_REGION }}
UPDATE_PRIVATE_KEY_PEM: ${{ secrets.UPDATE_PRIVATE_KEY_PEM }}
PLONDS_SIGNING_KEY: ${{ secrets.PLONDS_SIGNING_KEY }}
PDC_SIGNING_KEY: ${{ secrets.PDC_SIGNING_KEY }}
S3_ACCESS_KEY: ${{ secrets.S3_ACCESS_KEY }}
S3_SECRET_KEY: ${{ secrets.S3_SECRET_KEY }}
AWS_ACCESS_KEY_ID: ${{ secrets.S3_ACCESS_KEY }}
@@ -759,6 +760,9 @@ jobs:
$ErrorActionPreference = "Stop"
$key = $env:PLONDS_SIGNING_KEY
if ([string]::IsNullOrWhiteSpace($key)) {
$key = $env:PDC_SIGNING_KEY
}
if ([string]::IsNullOrWhiteSpace($key)) {
$key = $env:UPDATE_PRIVATE_KEY_PEM
}
@@ -775,7 +779,7 @@ jobs:
shell: bash
run: |
set -euo pipefail
aws --endpoint-url "$S3_ENDPOINT" --region "$S3_REGION" s3 ls "s3://$S3_BUCKET" --only-show-errors >/dev/null
aws --endpoint-url "$S3_ENDPOINT" --region "$S3_REGION" s3 ls "s3://$S3_BUCKET" >/dev/null
echo "S3 access probe succeeded for $S3_BUCKET"
- name: Build PLONDS assets