CVE Feed: Add Prow job link as a metadata field

[PushkarJ]

Description

Freshness of a feed is dependent on successful scheduled prow job runs. Adding a link to job in the "json" feed and the markdown description, allows folks to look at the prow job to ensure that prow job has been running successfully as recent as few hours ago.

Details

Add a field named "prow job", under the custom map of _kubernetes.io at the top of the feed (not part of each CVE item) with single value being "https://testgrid.k8s.io/sig-security-cve-feed#auto-refreshing-official-cve-feed"

[mtardy]

/kind feature

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[mtardy]

Add a field named "prow job", under the custom map of _kubernetes.io at the top of the feed (not part of each CVE item) with single value being "https://testgrid.k8s.io/sig-security-cve-feed#auto-refreshing-official-cve-feed"

Ah I was thinking that we wanted to link to the specific job that created the JSON itself, and I'm not sure we can do that simply. If it's just a hardcoded single value to the testgrid.k8s.io website, I guess it's fairly trivial! :)

/assign

[mtardy]

/remove-lifecycle stale

[PushkarJ]

/triage accepted
/sig security docs
/area security

[k8s-ci-robot]

@PushkarJ: The label(s) area/security cannot be applied, because the repository doesn't have them.

In response to this:

/triage accepted
/sig security docs
/area security

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.