Skip to content

Commit

Permalink
Transform CVE feed shortcode compliance check to warning
Browse files Browse the repository at this point in the history
Previously it would cause the build to fail, which could lead to
confusing situation since the CVE feed comes from outside of the website
and could break the workflow. See related discussion:
#38579 (comment)
  • Loading branch information
mtardy committed Feb 28, 2023
1 parent 3d850f6 commit aa9f17e
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion layouts/shortcodes/cve-feed.html
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
{{ $feed := getJSON .Site.Params.cveFeedBucket }}
{{ if ne $feed.version "https://jsonfeed.org/version/1.1" }}
{{ errorf "Build Failed. CVE feed does not comply with JSON feed v1.1" }}
{{ warnf "CVE feed shortcode. KEP-3203: CVE feed does not comply with JSON feed v1.1." }}
{{ end }}
<table class="security-cves">
<caption style="caption-side: top;">{{ T "cve_table" }} {{ printf (T "cve_table_date_format_string") ($feed._kubernetes_io.updated_at | time.Format (T "cve_table_date_format")) }}</caption>
Expand Down

0 comments on commit aa9f17e

Please sign in to comment.