Skip to content

refactor(exporters): read the exporter's style through its engine - #67

Merged
aaronlippold merged 1 commit into
nextfrom
refactor/fh9l16-exporter-config-property
Nov 19, 2026
Merged

aaronlippold merged 1 commit into
nextfrom
refactor/fh9l16-exporter-config-property

Conversation

@aaronlippold

Copy link
Copy Markdown
Member

XCCDFExporter.config is now a read-only property that returns engine.config, so the exporter no longer keeps a second copy of the style. An exporter given another engine now writes that engine's style. The three tests that rebound both now set only the engine.

Checks:

  • Full suite, tests/scripts, mypy, ruff and mkdocs build --strict pass.
  • All 28 exports are byte-identical to next and pass cis-bench validate.

Card: cis-bench-fh9l.16, a follow-up from the review of cis-bench-fh9l.9.

XCCDFExporter.config is a read-only property returning engine.config,
so the style has one home: an exporter given another engine writes that
engine's style, and tests no longer rebind both. The 28 exports are
byte-identical.

Refs: cis-bench-fh9l.16
Signed-off-by: Aaron Lippold <lippold@gmail.com>
@aaronlippold
aaronlippold merged commit 909b74f into next Nov 19, 2026
7 checks passed
@aaronlippold
aaronlippold deleted the refactor/fh9l16-exporter-config-property branch November 19, 2026 23:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant