Skip to content

PF-192: Pipeline job running > hour fails with expired creds #3240

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
gruntwork-ci wants to merge 2 commits into
base: main
Choose a base branch
from
Open

PF-192: Pipeline job running > hour fails with expired creds #3240

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a13cbc1
PF-192: Pipeline job running > hour fails with expired creds
Aug 7, 2026
299bfc1
fixing typo
x-nightwing Aug 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions docs/2.0/docs/pipelines/architecture/security-controls.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -63,6 +63,10 @@ See [Setup via Machine Users](/2.0/docs/pipelines/installation/viamachineusers)

Pipelines will also require access to Gruntwork's GitHub repositories, however those tokens are generated at runtime via the Gruntwork Management Portal.

These Gruntwork GitHub access tokens are short-lived, expiring one hour after they are issued. Every job that needs one obtains its own token from that job's OIDC identity, rather than inheriting a token issued once at the start of the pipeline, so pipelines that run for longer than an hour are not affected by token expiry.

If you set `PIPELINES_GRUNTWORK_READ_TOKEN` yourself as a CI/CD variable, Pipelines uses your token as-is and never replaces it. In that case the token's lifetime is entirely up to you.

</TabItem>
</Tabs>

Expand Down