neon/actions at 6f7aeaa1c563906fe14a4f62870d9fcd62436e02 - neon

rust/neon

mirror of https://github.com/neondatabase/neon.git synced 2026-01-08 22:12:56 +00:00

Files

Peter Bendel a8ac895b83 re-acquire S3 OIDC token after long running tests for report upload to S3 (#9799 )

## Problem

If a benchmark or test-case runs longer than the AWS OIDC token lifetime
successive upload of test reports to S3 fail - example:


https://github.com/neondatabase/neon/actions/runs/11905529176/job/33176168174#step:9:243

## Summary of changes

In actions that require access to S3 and which are invoked after a long
running python testcase we re-acquire the OIDC token explicitly.
Note that we need to pass down the aws_oicd_role_arn from the workflow
to the action because actions have no access to GitHub vars for security
reasons.

Sample run
https://github.com/neondatabase/neon/actions/runs/11912328276/job/33195676867

2024-11-19 18:22:51 +01:00

allure-report-generate

re-acquire S3 OIDC token after long running tests for report upload to S3 (#9799 )

2024-11-19 18:22:51 +01:00

allure-report-store

re-acquire S3 OIDC token after long running tests for report upload to S3 (#9799 )

2024-11-19 18:22:51 +01:00

download

add commit hash to S3 object identifier for artifacts on S3 (#8161 )

2024-06-26 05:46:52 +00:00

neon-branch-create

Fix typos in action definitions