Skip to content

feat: Support externaly stored CI badges - #741

Open
darkdoc wants to merge 3 commits into
validatedpatterns:mainfrom
darkdoc:external_badges
Open

darkdoc wants to merge 3 commits into
validatedpatterns:mainfrom
darkdoc:external_badges

Conversation

@darkdoc

@darkdoc darkdoc commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

Add badge for rhoso pattern

Add badge for rhoso pattern
@openshift-ci openshift-ci Bot added the size/L label Oct 6, 2026
@ocpdocs-previewbot

ocpdocs-previewbot commented Oct 6, 2026 •

Copy link
Copy Markdown

🤖 Tue Oct 27 15:25:02 - The preview is ready at:
https://741--patternsdocs-pr.netlify.app

@cjeanner cjeanner left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know I can't approve, but I do approve that change :). Thank you @darkdoc !

@openshift-ci

openshift-ci Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor

@cjeanner: changing LGTM is restricted to collaborators

Details

In response to this:

I know I can't approve, but I do approve that change :). Thank you @darkdoc !

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-sigs/prow repository.

@laubai

laubai commented Oct 15, 2026

Copy link
Copy Markdown
Contributor

Reviewed and posted question about sanitizing inputs in Slack.

@laubai
laubai requested review from laubai and removed request for gaurav-nelson October 16, 2026 01:38

@laubai laubai left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably need to sanitize inputs from external sources or add tests to reduce risk, e.g. say the JSON file listed at ci_source changes to include a malicious URL at either patternRepo or pipelineUrl, it doesn't currently look like we could catch that change before our site is updated with it.

@cjeanner

Copy link
Copy Markdown
Contributor

Probably need to sanitize inputs from external sources or add tests to reduce risk, e.g. say the JSON file listed at ci_source changes to include a malicious URL at either patternRepo or pipelineUrl, it doesn't currently look like we could catch that change before our site is updated with it.

Hey @laubai I'm wondering what are the actual risks there: as far as I know, pipelineUrl isn't used by validatedpattern.io website, is it? Meaning only human would click on that link, provided they open the JSON file. Maybe that specific key shouldn't even be in the badge (neither should the debugInfo imho, since it may point to internal resources).

Regarding the patternRepo, there, yes, a filter ensuring it's hosted under validatedpatterns or validatedpatterns-sandbox org is probably something that should be implemented, though I think it's not the one used to expose the link to the actual pattern either, since sandbox patterns may not have the badge, but are still showing the link to the source repository.

Any thoughts?

@laubai

laubai commented Oct 23, 2026

Copy link
Copy Markdown
Contributor

@cjeanner The test build doesn't include data/cards, so I wasn't sure about that - just raising out of caution.
In the current site, you can definitely get to the point of seeing pipelineURL and patternRepo values (on vp.io, click Status --> Classic --> click a badge) but we're not waving them in front of people.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants