Skip to content
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

Jump to bottom

Try to re-read secrets on error 401 #362

Closed
nuclearcat opened this issue Nov 28, 2023 · 1 comment
Closed

Try to re-read secrets on error 401 #362

nuclearcat opened this issue Nov 28, 2023 · 1 comment

Comments

@nuclearcat
Copy link
Member

As discussed in #359 we need to try re-reading secret file in case we received error 401 (invalid token). It is entirely possible that API instance got updated, token changed, and secret in pipeline updated as well.
@nuclearcat
Copy link
Member Author

Duplicate #358 (comment)

@nuclearcat nuclearcat closed this as not planned Won't fix, can't repro, duplicate, stale Nov 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nuclearcat