Skip to content
Snippets Groups Projects
Select Git revision
  • 78f4d0a348ed3a5c2c88d26638dae6a82a378aec
  • experimental default protected
  • v2023.2.5-ffs
  • nrb/ex400-remove-wps
  • nrb/airmax-test
  • v2023.2.4-ffs
  • nrb/ar9344-reset-sequence
  • autinerd/experimental-openwrt-24.10
  • v2023.2.3-ffs
  • v2023.2.2-ffs
  • v2023.2-ffs
  • v2023.1-ffs
  • v2022.1.4-ffs
  • feature/addMikrotikwAP
  • v2022.1.3-ffs
  • v2021.1.2-ffs
  • v2022.1.1-ffs
  • master protected
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • experimental-2025-07-04
  • experimental-2025-07-04-base
  • experimental-2025-07-01
  • experimental-2025-07-01-base
  • experimental-2025-06-25
  • experimental-2025-06-25-base
  • experimental-2025-06-24
  • experimental-2025-06-24-base
  • experimental-2025-06-22
  • experimental-2025-06-22-base
  • v2023.2.5-ffs0.1
  • experimental-2025-06-08
  • experimental-2025-06-08-base
  • experimental-2025-06-06
  • experimental-2025-06-06-base
  • experimental-2025-05-27
  • experimental-2025-05-27-base
  • experimental-2025-05-18
  • experimental-2025-05-18-base
  • experimental-2025-05-15
41 results

check_site.lua

  • Matthias Schiffer's avatar
    7ccdacd2
    treewide: rework check_site_lib.lua · 7ccdacd2
    Matthias Schiffer authored
    In addition to significant internal differences in check_site_lib.lua (in
    particular unifying error handling to a single place for the upcoming
    multi-domain support), this changes the way fields are addressed in site
    check scripts: rather than providing a string like 'next_node.ip6', the
    path is passed as an array {'next_node', 'ip6'}.
    
    Other changes in site check scripts:
    * need_array and need_table now pass the full path to the sub fields to the
    subcheck instead of the key and value
    * Any check referring to a field inside a table implies that all higher
    levels must be tables if they exist: a check for {'next_node', 'ip6'} adds
    an implicit (optional) check for {'next_node'}, which allows to remove many
    explicit checks for such tables
    treewide: rework check_site_lib.lua
    Matthias Schiffer authored
    In addition to significant internal differences in check_site_lib.lua (in
    particular unifying error handling to a single place for the upcoming
    multi-domain support), this changes the way fields are addressed in site
    check scripts: rather than providing a string like 'next_node.ip6', the
    path is passed as an array {'next_node', 'ip6'}.
    
    Other changes in site check scripts:
    * need_array and need_table now pass the full path to the sub fields to the
    subcheck instead of the key and value
    * Any check referring to a field inside a table implies that all higher
    levels must be tables if they exist: a check for {'next_node', 'ip6'} adds
    an implicit (optional) check for {'next_node'}, which allows to remove many
    explicit checks for such tables