chore: pass lifetime directly into api key generate #11715
Merged
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.
This was pulled out of #11609. I am trying to split up that PR so we can review and merge more easily.
Rather than passing all the deployment values, pass just the lifetime since that is all we use. This is to make it easier to generate API keys as part of the oauth flow (otherwise we will need send the deployment values into the identity provider).
I also added and fixed a test for when the lifetime is set and the default and expiration are unset (was just missing a multiplication by
time.Second
to use seconds instead of nanoseconds or whatever the default is).