main was 16 days and 259 commits behind the line the product is actually built on, at contract 0.30.0 against 0.35.0, with no per-PC credential code at all. It was neither current nor curated - just stale. This brings it forward and, at the same time, makes it mean something: main is what a receiving site installs, and nothing else. WHAT IT CARRIES. Twelve plugins - backups, computers, endpoints, guides, knowledgebase, machines, network, notifications, printers, slides, tools, warranty - plus applications, which is manifest-less core and always ships. The only manifest dependency inside that set is endpoints on computers, and both are in it, so the closure is self-contained. WHAT IT DOES NOT. employees, geenforce, measuringtools, printedparts and usb stay on the site line. So do the Windows installer tree, the VM rehearsal helpers, the agent tooling config, one site's data loader, the internal audit and findings records, and the planner spreadsheet. 1,135 tracked files against 1,438. A REMOVAL THAT BREAKS THE APP IS NOT A REMOVAL, and two nearly shipped: deploy/site-profile-universal.json still named all seventeen plugins. It is the file docs/DEPLOY.md tells a site to provision from, so a fresh install would have failed at `flask plugin apply-profile` with PluginError - the first thing a receiving site does, broken by the branch meant to serve them. It now names the twelve that exist, and its comment says the two must agree. agent/ was never refreshed. Whoever populated this branch copied shopdb/, plugins/, frontend/ and tests/ from the site line and left the agent tree at its September state: 22 C# and PowerShell sources missing, including AgentCredentials, EnrollmentService, AgentHttpFactory and the fleet-alert client, plus one file the site line had deleted still present. The old tree is internally consistent, so it compiles, and nothing in CI builds it - every gate was green over a server that speaks enrollment and per-PC credentials to a bundled agent source that cannot. Resynced whole. DECISIONS THIS ENCODES, rather than defers: - The plugin-authoring lab builds printedparts, whose manifest depends on employees, so it could not stay. The lab remains on the site line and main ships no build-along tutorial. That is a real loss for an adopting developer and is recorded here rather than discovered later. - Recognition, Training and Recertification notifications are no longer seeded. Each splits one notification into a card per employee and renders a photo, which needs a plugin this branch does not bundle. Seeding them would offer an author a type that cannot resolve anybody. A site that installs employees gets them from that plugin's own seed. - Windows/IIS is documented as the legacy path throughout, and the README leads with Docker, because that is what a receiving site gets. The API description is regenerated for THIS branch - 347 paths and 483 operations, down from 415 and 573 - so the published contract describes what is here rather than what the site line serves. docs/CONFIG.md lost the two measuring-tool label keys the code no longer declares, which two lanes had decided opposite ways. Suite: 3124 passed, 6 skipped. Naming and style gates pass. The docs gates run rather than skip, and every index line count is derived from the file it names.
95 lines
3.5 KiB
Python
95 lines
3.5 KiB
Python
"""Every setting a plugin declares must be reachable in its settings page.
|
|
|
|
A setting exists so a site can change it. One that is seeded into the database
|
|
but rendered by no page is not configurable - it is a constant with extra steps,
|
|
and the only way to change it is direct SQL.
|
|
|
|
This was written after shipping exactly that twice in one afternoon:
|
|
a plugin's kiosk_enabled / kiosk_token settings were declared
|
|
in get_settings(), seeded correctly, and read correctly by the API - and none of
|
|
them appeared on any page, because each settings view carries a hardcoded KEYS
|
|
list that nobody remembered to extend. The instructions for turning the kiosk
|
|
back on were impossible to follow.
|
|
|
|
The check is deliberately crude: it greps the plugin's frontend for the key as a
|
|
literal. That is enough to catch the failure it exists for, and it cannot be
|
|
satisfied by accident.
|
|
"""
|
|
|
|
import pathlib
|
|
import re
|
|
|
|
import pytest
|
|
|
|
|
|
REPO = pathlib.Path(__file__).resolve().parents[1]
|
|
PLUGINS = REPO / 'plugins'
|
|
|
|
# Settings a site is not meant to edit through a page. Each needs a reason.
|
|
EXEMPT = {
|
|
# Written by the app itself when the agent key is minted, not typed.
|
|
'plugin.endpoints.agentkeyprovisioned',
|
|
'plugin.endpoints.envkeyfallback',
|
|
# Edited on the endpoints Enrollment page through
|
|
# PUT /api/endpoints/enrollment/settings, not the generic settings view:
|
|
# turning the shared key off needs a confirm that shows how many PCs are
|
|
# not enrolled yet, which a plain settings field cannot give.
|
|
'plugin.endpoints.sharedkeyallowed',
|
|
'plugin.endpoints.autoenroll',
|
|
}
|
|
|
|
|
|
|
|
def _declared_settings(plugin_dir):
|
|
"""Keys the plugin declares in get_settings_defaults(), read from the source.
|
|
|
|
Importing the plugin would need an app context and a database; the
|
|
declaration is a literal list, so reading it is enough and much cheaper.
|
|
"""
|
|
source = (plugin_dir / 'plugin.py')
|
|
if not source.is_file():
|
|
return []
|
|
text = source.read_text(encoding='utf-8')
|
|
match = re.search(r'def get_settings_defaults\(self\).*?(?=\n def |\Z)', text, re.S)
|
|
if not match:
|
|
return []
|
|
return re.findall(r"'key':\s*'([^']+)'", match.group(0))
|
|
|
|
|
|
def _frontend_text(plugin_dir):
|
|
frontend = plugin_dir / 'frontend'
|
|
if not frontend.is_dir():
|
|
return ''
|
|
parts = []
|
|
for path in frontend.rglob('*'):
|
|
if path.suffix in ('.vue', '.js') and path.is_file():
|
|
parts.append(path.read_text(encoding='utf-8'))
|
|
return '\n'.join(parts)
|
|
|
|
|
|
PLUGIN_DIRS = sorted(
|
|
d for d in PLUGINS.iterdir()
|
|
if d.is_dir() and (d / 'manifest.json').is_file()
|
|
)
|
|
|
|
|
|
@pytest.mark.parametrize('plugin_dir', PLUGIN_DIRS, ids=lambda d: d.name)
|
|
def test_every_declared_setting_is_reachable_in_the_ui(plugin_dir):
|
|
declared = [k for k in _declared_settings(plugin_dir) if k not in EXEMPT]
|
|
if not declared:
|
|
pytest.skip('declares no settings')
|
|
|
|
frontend = _frontend_text(plugin_dir)
|
|
if not frontend:
|
|
pytest.skip('ships no frontend')
|
|
|
|
missing = [key for key in declared if key not in frontend]
|
|
assert not missing, (
|
|
'%s declares %d setting(s) that appear nowhere in its frontend, so a '
|
|
'site cannot change them without writing SQL:\n %s\n'
|
|
'Add them to the plugin settings view (its KEYS list AND a field), or '
|
|
'to EXEMPT in this file with a reason. There is no backlog list: the '
|
|
'seven this check found when it was written were all fixed, and it '
|
|
'stays that way.'
|
|
% (plugin_dir.name, len(missing), '\n '.join(missing)))
|