README
- ::equalInputError::equal
- ::to_stringInputError::to_string
- ::canonicalValue::canonical
- ::equalValue::equal
- ::flattenValue::flatten
- ::pointerValue::pointer
- ::stringifyValue::stringify
- ::to_jsonValue::to_json
V
execute
V
from_json
V
parse
V
run

moon_configweave

Layered configuration merge, interpolation and provenance audit

configweave

cli

moonbit

Download zip

Author

123123213weqw

Version

0.10.0

License

Apache-2.0

Repository

github.com/123123213weqw/moon-configweave

Last updated

16 days ago

Downloads

No dependencies

#Moon ConfigWeave

Layered configuration audit, implemented in MoonBit with a JSON CLI and reusable library API: merge configuration layers, resolve references, trace every value to the layer and file that set it, mask secrets, validate constraints, compare environments and export a canonical artifact.

Repository: https://github.com/123123213weqw/moon-configweave
Package: 123123213weqw/moon_configweave on mooncakes.io (registry versions are listed in CHANGELOG.md)
License: Apache-2.0
Release scope: 1.0.0 complete implementation of the scope defined in docs/proposal.md. The three proposed scenarios run end to end, the acceptance checks (100 reference-validated configuration sets, key-order invariance, masking, failure paths) are executable, and the remaining limits are listed in docs/boundaries.md. See CHANGELOG.md for what changed since 0.1.0.

#Implemented

Layer merge: recursive object merge in layer order with replace (default), append or unique array strategies, assignable per request or per JSON Pointer path; optional strict_types rejects type-changing overlays; nesting is limited to 128 levels.
Provenance: origins maps every JSON Pointer path to the ordered list of layers that contributed to it, shadowed names the layer each override replaced, and each layer may carry a source label (the host adapter uses the file name) echoed in the report.
Interpolation: ${env:NAME} and ${config:/json/pointer} references with optional :-literal fallbacks for absent targets; a whole-string reference keeps the referenced type, embedded references render scalars; cycles, missing references and depth limits are rejected.
Secrets: sensitive paths, sensitive_keys (every path ending in one of the key names) and secret_env names are redacted to ***, and secrecy propagates through scalar and container aliases; masked lists every redacted path; output is redacted unless reveal is true.
Constraints: required, type, enum, pattern (unanchored regex search), min_length/max_length (strings and arrays), min, max per path; the first violated clause is reported in a fixed order; unknown types, clauses and invalid patterns are rejected. operation: "infer" derives such a set from the resolved values observed after every layer (consistent type, enums for small string sets, numeric bounds, required), skipping masked paths so secrets never leak; the result is checked against every observation.
Diff (operation: "diff"): compares two redacted configurations, annotates each change with the origins on both sides, reports a masked_override when a hidden value's origin chain changed without revealing it, and drops changes under ignore pointers (build stamps, caches).
Export (operation: "export"): canonical JSON text (keys in UTF-16 code unit order, no whitespace) for stable artifacts and hashing, or format: "flat" (one entry per leaf keyed by JSON Pointer) or format: "dotenv" (KEY=value lines for deployment, secrets still masked).
Host adapter: scripts/files.py reads JSON and TOML layer files (Python 3.11+ tomllib), expands a dir entry into one layer per file in name order (conf.d style), and copies allow-listed environment variables; the engine never reads files itself.

#Build and run

Use MoonBit and Node.js 24. The core library supports JS, wasm, wasm-gc and native; the filesystem/process CLI is JS only.

moon update
moon build --target js
moon run cmd/main --target js -- examples/request.json        # a self-contained request
node _build/js/debug/build/cmd/main/main.js examples/request.json
python -B scripts/files.py examples/service/dev.manifest.json  # layer files + environment via the adapter

Pass - to read a UTF-8 JSON request from stdin. A single request must be at most 16 MiB. The CLI prints one JSON result and exits 0 for a valid report, 2 for a report whose constraints found issues (valid: false), and 1 after printing {"error": "..."} for a rejected request. The host adapter uses the same codes. Error messages name paths and variable names, never values.

#Library use

mooncakes.io currently accepts only zero-major versions (moon publish rejects anything else with "In this very early stage, the major version must be '0'"), so repository releases and registry versions are numbered separately. The registry version corresponding to each repository release is recorded in CHANGELOG.md; 0.1.0 is the initial implementation.

moon add 123123213weqw/moon_configweave@0.10.0

In the consumer's moon.pkg:

import {
  "123123213weqw/moon_configweave" @engine,
  "moonbitlang/core/json",
}

fn example(request : Json) -> Json raise {
  @engine.execute(request)
}

execute(Json) -> Json raise is the standard JSON boundary. parse(StringView) -> Value raise, from_json(Json) -> Value, Value::to_json and run(Value) -> Value raise provide a typed semantic value interface, and Value::flatten (leaf values by JSON Pointer), Value::pointer (lookup by JSON Pointer) and Value::canonical (canonical JSON text) help consumers work with reports. Object key order in requests is not significant; numeric values are finite doubles. The public interface is listed in pkg.generated.mbti.

#Requests and results

A merge request has layers (each {name, value, source?}), and optionally arrays (a strategy name or a per-path map), strict_types, env, secret_env, sensitive, sensitive_keys, constraints and reveal. The result has config, redacted, masked, shadowed, origins, layers, issues and valid. operation: "infer" takes a merge request plus an optional max_enum (1-64, default 8) and returns constraints that every observation satisfies. operation: "diff" takes old and new requests and an optional ignore list of pointers; operation: "export" takes a merge request plus an optional format (json, flat, dotenv) and returns text. Every documented case in docs/usage.md is an executable fixture.

#Scenarios

The three scenarios from the proposal live in examples/ as real input files with manifests, and scripts/scenarios.py runs all of them and checks their documented outcomes:

Scenario	Inputs	What the output shows
examples/service	TOML defaults, dev/prod JSON overrides, a database password from the environment	deployable dev config; a wrong "5432" string override in prod located at /database/port with origins defaults → prod; a dev/prod diff
examples/ci	base job plus linux/macos/windows overlays	append vs unique step and target merges; a Windows type conflict rejected under strict_types or reported as an issue; a stable single-line export
examples/tenants	app defaults, organization TOML policy, two tenant overrides	three-level resolution; tenant-b's rate limit and auth downgrade flagged; its hardcoded signing key reported as a masked_override without revealing it

See docs/scenarios.md for the inputs, decision process and verifiable outputs of each scenario.

#Tests and verification

moon check --deny-warn --target js      # zero warnings on every backend
moon test --target js                   # 38 tests: 33 fixture cases + property tests
moon test --target wasm
moon test --target wasm-gc
moon test --target native               # requires a C compiler
moon build --target js
node scripts/check.mjs                  # the 33 fixtures through the real CLI
python -B scripts/reference.py          # 100 configuration sets vs an independent Python oracle
python -B scripts/integration.py        # TOML/JSON files, directory layers, environment allowlist, adapter errors
python -B scripts/scenarios.py          # the three scenarios, 43 checks
python -B scripts/bench.py --check       # scale: 24k-key merge, 1000 references, depth 100
python -B scripts/fixtures.py --check   # generated tests and usage guide match tests/cases.json
python -B scripts/stats.py              # source statistics by category
sh scripts/consume.sh REGISTRY_VERSION  # fresh module consumes the published package

tests/cases.json is the single source of the 33 fixture cases; scripts/fixtures.py generates fixtures_wbtest.mbt and docs/usage.md from it. The oracle in scripts/reference.py is a separate Python implementation of the documented semantics; it checks merged values (global and per-path array strategies), origins, shadowed overrides, fallback references, masked paths, constraint verdicts, export text, key-order invariance, diff output and secret masking over 100 generated environment/tenant configuration sets whose keys include unicode and RFC 6901 escapes, then the failure paths (cycle, missing variable, type conflict, array strategy, deep paths). Fixtures and scenario data are synthetic and are not presented as production adoption evidence. CI runs all of the above on every push, the scale check included; the consumption check runs on demand against a registry version. Recorded benchmark observations live in docs/benchmarks.md.

#Current boundaries

Core input is JSON values; TOML is parsed by the optional Python 3.11+ host adapter. Secret fields (by path or by key name) and secret environment variable names must be designated explicitly. Default output is redacted; reveal=true explicitly returns plaintext. Diff compares redacted values: a change between two hidden secrets is only visible when its origin chain changed. Per-path array strategies match exact pointers only. There is no schema standard implementation, no escape sequence for a literal ${, and no remote configuration source. TOML date/time values cannot be represented by the JSON adapter and are rejected. See docs/boundaries.md.

See source and dependency attribution. This release does not establish competition eligibility or organizer acceptance.

#2026-10-18 follow-up

同步保留最新公开实现的层合并、来源、约束、推断、导出和环境差异能力，新增 audit：只报告路径、类型、脱敏状态及来源层，不输出配置值。即使 reveal=true，audit 仍使用 redacted 结果；被遮蔽的容器在边界停止展开。严格校验 JSON Pointer 转义及规范数组下标。

值本身不进入审计结果，但路径和层名仍是调用方提供的元信息。audit 不是秘密自动发现器；敏感字段须正确指定。约束及导出仍以现有受支持语义为准，TOML 由宿主 Python 标准库读取。

Repository release: 1.1.0; installable MoonCakes module: 123123213weqw/moon_configweave@0.10.0. Earlier repository 1.0.0 labels are retained as history; the module uses the registry-compatible zero-major sequence.

Current source contains 75 MoonBit test declarations and 66 CLI fixtures (generated fixture tests are included in the declaration count). Run python -B scripts/followup_reference.py for independent follow-up oracles and examples/followup-20261018.json for the new scenario.

InputError

source

pub(all) suberror InputError {
  InputError(String)
} derive(Eq)

impl Show for InputError

InputError::equal

source

fn InputError::equal(InputError, InputError) -> Bool

InputError::to_string

source

fn InputError::to_string(self : InputError) -> String

Value

source

pub(all) enum Value {
  Null
  Bool(Bool)
  Number(Double)
  String(String)
  Array(Array[Value])
  Object(Map[String, Value])
} derive(Eq, @moonbitlang/core/debug.Debug
Debug)

Value::canonical

source

fn Value::canonical(self : Value) -> String

Canonical JSON text: object keys in UTF-16 code unit order, no whitespace, arrays in order.

Value::equal

source

fn Value::equal(Value, Value) -> Bool

Value::flatten

source

fn Value::flatten(self : Value) -> Map[String, Value]

Maps every leaf (a scalar or an empty container) to its JSON Pointer path. The root path is "" and keys are escaped as in RFC 6901.

Value::pointer

source

fn Value::pointer(self : Value, path : String) -> Value raise

Returns the value at a JSON Pointer path, raising an input error when the path is malformed or absent.

Value::stringify

source

fn Value::stringify(self : Value) -> String

Value::to_json

source

fn Value::to_json(self : Value) -> Json

execute

source

fn execute(request : Json) -> Json raise

from_json

source

fn from_json(value : Json) -> Value

parse

source

fn parse(source : StringView) -> Value raise

Parses JSON text into a semantic value.

run

source

fn run(request : Value) -> Value raise

Source Files

Install

Download zip

Layered configuration merge, interpolation and provenance audit

configweaveclimoonbit

123123213weqw

Apache-2.0

github.com/123123213weqw/moon-configweave

Updated 16 days ago

39 downloads

Site source Report issue Modules Skills Build queue Statistics

moon_configweave

#Moon ConfigWeave

#Implemented

#Build and run

#Library use

#Requests and results

#Scenarios

#Tests and verification

#Current boundaries

#2026-10-18 follow-up

#InputError

#InputError::equal

#InputError::to_string

#Value

#Value::canonical

#Value::equal

#Value::flatten

#Value::pointer

#Value::stringify

#Value::to_json

#execute

#from_json

#parse

#run

Source Files

InputError

InputError::equal

InputError::to_string

Value

Value::canonical

Value::equal

Value::flatten

Value::pointer

Value::stringify

Value::to_json

execute

from_json

parse

run