Provide expiration information for cached results

[fridex]

Is your feature request related to a problem? Please describe.

As a user of Thoth, I would like to know when the cached result expires. To support this, I would like to access such information when asking for results.

Describe the solution you'd like

Provide information when the cached result expires (ex. in HTTP headers).

[goern]

/priority important-soon
/help

[sesheta]

@goern:
This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

Details

In response to this:

/priority important-soon
/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[goern]

@fridex could this be part of the meta information work?

/sig stack-guidance
/remove-lifecycle stale
/triage needs-information

[fridex]

Not sure what meta information work you are referring to. If the justification metadata extension we discussed then I don't think so. The cache is maintained by user-api so user-api can expose expiration info to users (regardless of the results returned). Applies to advises and package-extract results.

[sesheta]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[mayaCostantini]

/remove-lifecycle stale