LogoLogo
HomeBlogGet a Demo
  • Introduction
  • Install Lunar
  • Learn the basics
  • 📖Docs
    • Key concepts
    • Component JSON
    • Catalog JSON
    • Lunar CLI Reference
  • 📝Configuration
    • lunar-config.yml
      • catalogers
      • catalogers/hooks
      • domains
      • components
      • collectors
      • collectors/hooks
      • policies
    • lunar.yml
  • 🛠️Plugin SDKs
    • Plugins configuration
      • lunar-cataloger.yml
      • lunar-collector.yml
      • lunar-policy.yml
    • Bash SDK
      • Cataloger
      • Collector
    • Python SDK
      • Collector
      • Policy
        • Check
        • Path
        • ComponentData
        • NoDataError
        • Utility Functions
  • ⚙️SQL API
    • Overview
    • Views
      • domains
      • components
      • component_deltas
      • initiatives
      • policies
      • checks
      • prs
      • catalog
Powered by GitBook

©️ Earthly Technologies

On this page
  1. Plugin SDKs
  2. Python SDK
  3. Policy

NoDataError

The NoDataError exception is used to indicate that required data for a policy check is missing. This exception is automatically caught by the Check context manager, which sets the check status to "no-data".

The purpose of NoDataError is to distinguish between:

  1. Missing Data: When required data is not present (results in "no-data" status)

  2. Failed Assertions: When data is present but doesn't meet the policy requirements (results in "fail" status)

This distinction is important because Lunar re-evaluates policies as data becomes available. A "no-data" status indicates that the policy should be re-evaluated when more data is collected, while a "fail" status indicates a definitive policy violation.

Constructor

NoDataError(message=None)
  • message (str, optional): A message describing why the data is missing

PreviousComponentDataNextUtility Functions

Last updated 17 hours ago

🛠️