-
Notifications
You must be signed in to change notification settings - Fork 0
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
TSPS-401 add output expiration date to getPipelineRunResult response #187
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think this approach makes sense, a couple comments/suggestions
import org.springframework.boot.context.properties.ConfigurationProperties; | ||
|
||
@ConfigurationProperties(prefix = "pipelines.common") | ||
public record PipelinesCommonConfiguration(Long storageBucketTtlDays) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we already have WdlPipelinesConfiguration
, which contains stuff about quotas. Now that I think about it, quotas won't necessarily be specific to WdlPipelines - I like PipelinesCommonConfiguration
better for that too. what do you think about merging the quota config stuff into this one?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oh good point i totally forgot there was a WdlPipelinesConfiguration. let me see what each of them have and think about it a bit
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea let me move it al to this new configuration and see what it looks liek then!
import org.springframework.boot.context.properties.ConfigurationProperties; | ||
|
||
@ConfigurationProperties(prefix = "pipelines.common") | ||
public record PipelinesCommonConfiguration(Long storageBucketTtlDays) {} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any reason for this to be a Long vs an Integer?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
its onlly cuz the Instant.plus()
function takes in a Long value and not an int
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one variable renaming request but otherwise looks great!
private Long quotaConsumedPollingIntervalSeconds; | ||
private boolean quotaConsumedUseCallCaching; | ||
private Long storageBucketTtlDays; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor, but could we name this something other than "storageBucket" since that's also the term we use for where we store the ref panel. maybe "userDataTtlDays" (I considered "outputTtlDays" but this applies to user inputs too)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yea much better, changing
|
Description
On successful runs, we want the service to return the expected expiration date of when the outputs will be deleted. This will help the user know by when they should download their data by.
Jira Ticket
https://broadworkbench.atlassian.net/browse/TSPS-401
example response from the getPipelineRunResult api on a successful run
example of a non successful run