Remediation plans and pull requests

Experimental feature

Remediation plans and fix pull requests are experimental features. Their configuration, notifications, and PR formats may change.

Overview

Remediation plans propose image and dependency updates based on findings from images running with Docker and Compose. Enabling fix pull requests also creates GitHub PRs for eligible updates.

You are responsible for checking changes, merging, pulling or building images, deploying, and checking the deployment. For details, see Execution scope of plans and PRs.

Contents

• Enabling remediation
  • Enabling remediation plans
  • Enabling fix pull requests
• When no candidate or pull request appears
  • Collecting diagnostics
  • Checking for a missing plan
  • Checking update failures
  • Checking for a missing PR
  • Checking record reconciliation failures
• Reading the results
  • Remediation plans in Slack
  • Interpreting update results
  • Finding detailed results
• How candidate selection and PR processing work
  • Processing flow
  • Image candidate selection
  • Language package candidate selection
  • Runtime selection
  • Work container execution
  • Accepting update results
  • PR management
• Supported formats and reason codes
  • Scope and requirements
  • Supported input formats
  • Supported runtimes
  • Result values
  • Reason codes
  • Stored records

Related configuration and specifications are on the following pages.

• Configuration: Remediation plans and fix pull requests
• How KestreLynx works: Notification conditions
• How KestreLynx works: Generic webhook remediation fields
• How KestreLynx works: Outbound connections