Deploy: refresh token if close to expiry#228
Merged
itowlson merged 1 commit intofermyon:mainfrom May 21, 2025
Merged
Conversation
Signed-off-by: itowlson <ivan.towlson@fermyon.com>
bacongobbler
approved these changes
May 21, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #225.
Per discussion there, this now refreshes the token if it is within 5 minutes of expiry. So we should be safe for deployment operations that last less than 5 minutes, and less likely to suffer mid-operation expiry even on very long-running operations.
Tested by setting the "must have remaining" time to 28 minutes and verifying that it refreshed after 2 minutes.