534f179ee6
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.
49 lines
1.8 KiB
Python
49 lines
1.8 KiB
Python
"""Add scripts captureoutput
|
|
|
|
Backs the per-script "may a successful run send its output back" field.
|
|
|
|
The agent already captures a script's full output and always writes it to the
|
|
endpoint log. What this controls is narrower: whether that output also crosses
|
|
to the server and is persisted in the command's resultjson, where the Run
|
|
Scripts history can show it.
|
|
|
|
Failures have always sent output and still do - a failed run has to be
|
|
diagnosable without walking to the machine. Success is the case in question,
|
|
and it is opt-in because output carries whatever the body happened to print:
|
|
hostnames, share paths, an account name, a token an author echoed while
|
|
debugging. Accepting that exposure for every routine green run is a poor
|
|
trade, so the author decides per script, after reading the body.
|
|
|
|
BOOLEAN NOT NULL defaulting FALSE, so every script row written before this
|
|
migration keeps exactly today's behaviour: metadata on success, output only on
|
|
failure. Same rule as errormode - never retroactive, because a library-wide
|
|
flip would start persisting output from bodies nobody re-read with this
|
|
question in mind.
|
|
|
|
Revision ID: 7d50_script_captureoutput
|
|
Revises: 7d49_script_errormode
|
|
Create Date: 2026-09-09
|
|
|
|
"""
|
|
from alembic import op
|
|
import sqlalchemy as sa
|
|
|
|
|
|
revision = '7d50_script_captureoutput'
|
|
down_revision = '7d49_script_errormode'
|
|
branch_labels = None
|
|
depends_on = None
|
|
|
|
|
|
def upgrade():
|
|
op.add_column('scripts', sa.Column(
|
|
'captureoutput', sa.Boolean(), nullable=False,
|
|
server_default=sa.false(),
|
|
comment='When true, a successful run also returns its output to the '
|
|
'server; failures always do. Off by default because script '
|
|
'output can contain whatever the body printed.'))
|
|
|
|
|
|
def downgrade():
|
|
op.drop_column('scripts', 'captureoutput')
|