Pipeline run API token fixes and improvements #3242
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.
Describe changes
Two changes are included in this PR:
ZENML_PIPELINE_API_TOKEN_EXPIRATION
to a positive number of seconds. There is a maximum value that this can be set to, which is controlled by the server, configurable and has a default value of 1 week.The new
ZENML_PIPELINE_API_TOKEN_EXPIRATION
configuration option allows users to extend the validity of API tokens issued and attached to pipeline runs past the completion of the pipeline run, so that they may be able to re-run the pipeline run using external means, such as orchestrator dashboards.Pre-requisites
Please ensure you have done the following:
develop
and the open PR is targetingdevelop
. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.Types of changes