@davesheffer/hunch 1.45.2 → 1.47.0

package/dist/extractors/k8sManifest.d.ts

@@ -1,25 +1,3 @@
-/**
- * Deterministic text scan for Kubernetes manifest cross-resource references —
- * NOT a tree-sitter walk. Confirmed directly (not assumed): parsing a realistic
- * templated Deployment with this repo's own tree-sitter-yaml bundle showed a
- * same-line templated scalar (`name: {{ include "x" . }}`) parses cleanly, but
- * a block-form injection on its own line (`labels:\n  {{- include ... }}` — the
- * pattern real charts use for metadata.labels and spec.selector) collapses the
- * WHOLE REST OF THE DOCUMENT'S error recovery into a flat, unstructured ERROR
- * node. Real charts place such an injection early (right after metadata.name),
- * so it would poison parsing for every field-path this module needs further
- * down the same document. parseSource() (parse.ts) also never exposes its
- * tree-sitter tree to callers at all -- helm.ts's own text-scan precedent
- * exists for the same reason.
- *
- * This is a line-oriented, indentation-tracking scanner (not flat regex, unlike
- * helm.ts's `{{ }}`-action scan) because K8s field-paths are nested block
- * structure (`spec.template.spec.containers[].env[].valueFrom.secretKeyRef.name`)
- * that a flat scan can't reconstruct. It never interprets `{{ }}` as YAML syntax
- * at all -- a `{{ ... }}` on a line's value side is just that line's raw value
- * text, same-line or block-form alike -- so it is immune to the exact failure
- * mode that broke tree-sitter.
- */
 export type ManifestNameRef = {
     form: "literal";
     value: string;
@@ -31,72 +9,37 @@ export type ManifestNameRef = {
     atChar: number;
     endChar: number;
 };
-interface K8sReferenceCandidate {
-    /** Fixed literal for most kinds ("ConfigMap", "Secret", "PersistentVolumeClaim",
-     *  "Service"); for an ownerReferences entry, the reference's OWN `kind` field
-     *  value (data-dependent, not statically known). */
-    refKind: string;
-    name: ManifestNameRef;
-    /** The namespace this reference resolves IN, or null for "unknown" (see
-     *  literalNamespace). Kubernetes name references are same-namespace by
-     *  definition, so this defaults to the referring DOCUMENT's own namespace;
-     *  the one shape that can legitimately point elsewhere (a Gateway API
-     *  `backendRefs[].namespace` sibling) overrides it. */
-    namespace: string | null;
+export interface K8sManifestDocument {
+    resource: {
+        kind: string;
+        name: ManifestNameRef;
+        namespace: string | null;
+        startChar: number;
+        endChar: number;
+    } | null;
+    references: Array<{
+        refKind: string;
+        name: ManifestNameRef;
+        namespace: string | null;
+    }>;
+    selector: Record<string, string> | null;
+    labels: Record<string, string> | null;
 }
-type ManifestLabelMap = Record<string, string>;
-interface K8sResourceDoc {
-    kind: string;
-    name: ManifestNameRef;
-    /** `metadata.namespace` when it is a plain literal, else null = UNKNOWN (see
-     *  literalNamespace). Cluster-scoped kinds need no special case: they simply
-     *  never carry the field, so they are unknown and compatible with anything. */
+export interface KustomizationInfo {
     namespace: string | null;
-    startChar: number;
-    endChar: number;
-}
-export interface K8sManifestDocument {
-    resource: K8sResourceDoc | null;
-    references: K8sReferenceCandidate[];
-    selector: ManifestLabelMap | null;
-    labels: ManifestLabelMap | null;
+    resources: string[];
 }
-/** Namespace compatibility per the product rule: a MISSING (unknown) namespace
- *  matches anything; two DIFFERENT literal namespaces block the edge. */
-export declare function namespacesCompatible(a: string | null, b: string | null): boolean;
-/** Where a kind's pod spec lives -- factored once so container/volume field
- *  paths below aren't hand-duplicated per kind. */
 export declare const POD_SPEC_PATH_BY_KIND: Record<string, string>;
 export declare const LABELS_PATH_BY_KIND: Record<string, string>;
-/** `namespace` is a Kustomize transformer namespace for this file (from
- *  kustomizeNamespaces): undefined = no transformer, null = UNKNOWN (two
- *  kustomizations render this file into different namespaces). */
 export declare function extractK8sManifest(source: string, opts?: {
     namespace?: string | null;
 }): K8sManifestDocument[];
-export interface KustomizationInfo {
-    /** Top-level `namespace:` when it is a valid literal namespace, else null. */
-    namespace: string | null;
-    /** `resources:` entries exactly as written (paths relative to the kustomization's directory). */
-    resources: string[];
-}
+export declare function namespacesCompatible(a: string | null, b: string | null): boolean;
 export declare function isKustomizationFile(path: string): boolean;
-/** Reads only the two top-level fields the namespace transformer needs:
- *  `namespace:` and the `resources:` list (block `- item` lines or a one-line
- *  flow `[a, b]`). One linear pass; everything else in the file is ignored. */
 export declare function extractKustomization(source: string): KustomizationInfo;
-/** The Kustomize namespace each manifest file is rendered into, keyed by repo
- *  path. `kustomizations` is keyed by the kustomization's DIRECTORY ("" for
- *  the repo root); `files` is the indexed file set.
- *
- *  A `resources:` entry naming a file applies the namespace to that file; an
- *  entry naming a directory that holds its own kustomization is a base, and
- *  the referring (outer) kustomization's namespace wins over the base's, as
- *  Kustomize applies the overlay transformer to the base's output. Only
- *  kustomizations no other kustomization references are rendered as roots.
- *  A file rendered into two different namespaces (one base shared by dev and
- *  prod overlays, the common layout) maps to null = UNKNOWN; a file rendered
- *  only without any transformer is absent. Not modelled: remote resources,
- *  `components:`, the deprecated `bases:` field, and globs. */
+/**
+ * Effective namespace per manifest file after Kustomize's namespace transformer.
+ * A file reached with conflicting namespaces maps to null; a file that is only
+ * ever kept as written (or never rendered) is absent.
+ */
 export declare function kustomizeNamespaces(kustomizations: ReadonlyMap<string, KustomizationInfo>, files: ReadonlySet<string>): Map<string, string | null>;
-export {};