@scoutflo/topology-contracts 0.5.1 → 0.6.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +5 -1
- package/dist/src/investigation/context.d.ts +126 -126
- package/dist/src/providers/aliases.d.ts +1 -1
- package/dist/src/providers/providers.d.ts +4 -2
- package/dist/src/providers/providers.js +4 -0
- package/dist/src/providers/providers.js.map +1 -1
- package/dist/src/source-sync/candidate.d.ts +47 -47
- package/dist/src/source-sync/capability.d.ts +3 -3
- package/dist/src/source-sync/intent.d.ts +12 -12
- package/dist/src/source-sync/lifecycle.d.ts +9 -9
- package/dist/src/source-sync/scope.d.ts +3 -3
- package/dist/src/topology/relationTypes.d.ts +31 -5
- package/dist/src/topology/relationTypes.js +60 -6
- package/dist/src/topology/relationTypes.js.map +1 -1
- package/dist/src/topology/resourceTypes.d.ts +25 -7
- package/dist/src/topology/resourceTypes.js +48 -10
- package/dist/src/topology/resourceTypes.js.map +1 -1
- package/dist/test/contracts.test.js +33 -0
- package/dist/test/contracts.test.js.map +1 -1
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -8,7 +8,11 @@ This package owns:
|
|
|
8
8
|
- AWS, Kubernetes, and integration topology family constants;
|
|
9
9
|
- source-sync capability, intent, scope, completeness, warning, and candidate DTO schemas;
|
|
10
10
|
- topology correlation rule metadata and candidate DTO schemas;
|
|
11
|
-
-
|
|
11
|
+
- Gateway/Mongo-aligned topology resource and relation vocabulary constants useful at contract boundaries.
|
|
12
|
+
|
|
13
|
+
Canonical topology resource and relation constants mirror stable persisted Scoutflo ontology values. Source-sync family constants remain separate and may use provider/source-specific family names such as AWS scan families.
|
|
14
|
+
|
|
15
|
+
Provider constants are shared vocabulary, not a source-sync capability registry. Values such as `pagerduty` and `correlation` may be valid persisted providers without implying that the source-sync registry can run them.
|
|
12
16
|
|
|
13
17
|
Gateway remains the runtime authority for provider discovery, credential resolution, dry-run/apply, lifecycle, reconciliation, persistence, audit, provider clients, source-specific payload parsing, and topology correlation rule execution.
|
|
14
18
|
|