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.

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

refactor(vault): Remove an unneeded runBlocking call #562

Merged

Conversation

oheger-bosch
Copy link
Contributor

Rework the token handling to not fetch a token initially, but deal with a missing token during request execution. While this slightly makes the logic more complex, it has the benefits that during creation of a VaultSecretsProvider instance no request is sent, and the runBlocking call to fetch the initial token can be dropped.

@sschuberth
Copy link
Contributor

Commit message nits:

  • "While this slightly makes the logic more complex" -> "While this makes the logic slightly more complex"
  • Probably singular "benefit"

Rework the token handling to not fetch a token initially, but deal
with a missing token during request execution. While this makes the
logic slightly more complex, it has the benefit that during creation
of a `VaultSecretsProvider` instance no request is sent, and the
`runBlocking` call to fetch the initial token can be dropped.

Signed-off-by: Oliver Heger <[email protected]>
@oheger-bosch oheger-bosch added this pull request to the merge queue Jul 3, 2024
Merged via the queue into eclipse-apoapsis:main with commit f695828 Jul 3, 2024
12 checks passed
@oheger-bosch oheger-bosch deleted the vault_token_handling branch July 3, 2024 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants