Skip to content
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.

Sign up for GitHub

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

Jump to bottom

ci: temporarily disable container scan with Trivy #468

Merged
merged 4 commits into from
Sep 22, 2024
Merged

ci: temporarily disable container scan with Trivy #468

merged 4 commits into from
Sep 22, 2024

Conversation

ppawlowski
Copy link
Contributor

@ppawlowski ppawlowski commented Sep 22, 2024 •
edited
Loading

Description

This pull request temporarily disable container images scanning with Trivy due to the known issue.

Related Issue(s)

Checklist

  • I have read the contribution guidelines
  • Suitable unit/system level tests have been added and they pass
  • Documentation has been updated
    • Upgrade instructions
    • Configuration details
    • Concepts
  • Changes flowforge.yml?
    • Issue/PR raised on FlowFuse/helm to update ConfigMap Template
    • Issue/PR raised on FlowFuse/CloudProject to update values for Staging/Production

Labels

  • Includes a DB migration? -> add the area:migration label

@ppawlowski ppawlowski changed the title test: trivy action ci: temporarily disable container scan with Trivy Sep 22, 2024
@ppawlowski ppawlowski marked this pull request as ready for review September 22, 2024 20:38
@ppawlowski ppawlowski requested a review from hardillb September 22, 2024 20:38
@hardillb hardillb merged commit 694123a into main Sep 22, 2024
28 checks passed
@hardillb hardillb deleted the ci-test-trivy-action branch September 22, 2024 20:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@hardillb hardillb hardillb approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@ppawlowski @hardillb