Skip to content

ethanfox — dismiss vulnerabilities documentation#44663

Draft
ethanfox wants to merge 3 commits intofleetdm:mainfrom
ethanfox:ethanfox-dismiss-vulnerabilities-documentaion
Draft

ethanfox — dismiss vulnerabilities documentation#44663
ethanfox wants to merge 3 commits intofleetdm:mainfrom
ethanfox:ethanfox-dismiss-vulnerabilities-documentaion

Conversation

@ethanfox
Copy link
Copy Markdown
Contributor

@ethanfox ethanfox commented May 4, 2026

UPDATE: @noahtalerman: This PR is part of the design challenge for the Product Designer role.


Related issue: Resolves #

Checklist for submitter

If some of the following don't apply, delete the relevant line.

  • Changes file added for user-visible changes in changes/, orbit/changes/ or ee/fleetd-chrome/changes.
    See Changes files for more information.

  • Input data is properly validated, SELECT * is avoided, SQL injection is prevented (using placeholders for values in statements), JS inline code is prevented especially for url redirects, and untrusted data interpolated into shell scripts/commands is validated against shell metacharacters.

  • Timeouts are implemented and retries are limited to avoid infinite loops

  • If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes

Testing

For unreleased bug fixes in a release candidate, one of:

  • Confirmed that the fix is not expected to adversely impact load test results
  • Alerted the release DRI if additional load testing is needed

Database migrations

  • Checked schema for all modified table for columns that will auto-update timestamps during migration.
  • Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects.
  • Ensured the correct collation is explicitly set for character columns (COLLATE utf8mb4_unicode_ci).

New Fleet configuration settings

  • Setting(s) is/are explicitly excluded from GitOps

If you didn't check the box above, follow this checklist for GitOps-enabled settings:

  • Verified that the setting is exported via fleetctl generate-gitops
  • Verified the setting is documented in a separate PR to the GitOps documentation
  • Verified that the setting is cleared on the server if it is not supplied in a YAML file (or that it is documented as being optional)
  • Verified that any relevant UI is disabled when GitOps mode is enabled

fleetd/orbit/Fleet Desktop

  • Verified compatibility with the latest released version of Fleet (see Must rule)
  • If the change applies to only one platform, confirmed that runtime.GOOS is used as needed to isolate changes
  • Verified that fleetd runs on macOS, Linux and Windows
  • Verified auto-update works from the released version of component to the new version (see tools/tuf/test)

ethanfox added 3 commits May 4, 2026 09:53
Added sections for dismissing and restoring vulnerabilities in the API documentation.
Added documentation for dismissed vulnerabilities configuration in YAML files, including examples for inline and separate file usage.
Copilot AI review requested due to automatic review settings May 4, 2026 15:32
@ethanfox ethanfox requested a review from rachaelshaw as a code owner May 4, 2026 15:32
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

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

Claude Code Review

This pull request is from a fork — automated review is disabled. A repository maintainer can comment @claude review to run a one-time review.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Copilot wasn't able to review any files in this pull request.


💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@rachaelshaw rachaelshaw added the ~api-or-yaml-design Used for pull requests (PRs) with proposed API and YAML changes label May 4, 2026
@noahtalerman
Copy link
Copy Markdown
Member

UPDATE: @noahtalerman: This PR is part of the design challenge for the Product Designer role.

@ethanfox looking good! Excited to review w/ you live during our next call. FYI Marked this PR as draft and left above note at the top so other folks know what it's for.

@noahtalerman noahtalerman marked this pull request as draft May 4, 2026 22:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

~api-or-yaml-design Used for pull requests (PRs) with proposed API and YAML changes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants