chore(deps): update dependency arnarg/nixidy to v0.23.1 #61

Merged
martin merged 2 commits from renovate/arnarg-nixidy-0.x into main 2026-10-18 17:34:54 +00:00
Member

This PR contains the following updates:

Package Update Change
arnarg/nixidy minor v0.22.1 → v0.23.1

Release Notes

arnarg/nixidy (arnarg/nixidy)

v0.23.1

Compare Source

This is a small bugfix release.

Bug Fixes

  • Function replace in objectTransforms is now applied instead of wrapped. The replace option's type coercion accepted functions as plain values, so a lambda like replace = old: old // { ... }; was returned as-is instead of being called with the old object. The coerced type now excludes functions, so function replaces transform the matched object (or part) again, while plain values keep being coerced to _: value. @​sini #​112

v0.23.0

Compare Source

New Features

Object Transforms, reimagined: transform parts of resources - @​mewp #​109

The object transform mechanism has been completely reworked and is far more powerful now. Instead of a list of rules with a rewrite function, objectTransforms is an attrset where each transform can act on a whole resource or on just a part of it:

{
  nixidy.objectTransforms = {
    # Match objects, then update a part of them.
    fix-store = {
      match.kind = "ExternalSecret";
      update.spec.secretStoreRef = {
        kind = "ClusterSecretStore";
        name = "foo";
      };
    };

    # Target a specific path inside every matched resource. List elements
    # are iterated, so this rewrites every container in every Deployment:
    add-tty = {
      match.kind = "Deployment";
      transforms.tty = {
        path = [ "spec" "template" "spec" "containers" ];
        update.tty = true;
      };
    };

    # Setting a part to null removes the attribute.
    drop-foo-label = {
      path = [ "metadata" "labels" "foo" ];
      replace = null;
    };
  };
}

Each transform sets exactly one of replace (swap the value or the whole object, returning null drops it), update (recursively merge into the old value), or transforms (nested transforms, scoped to what the outer transform matched and nestable arbitrarily deep). Plain values are accepted anywhere a function is, so replace = { ... }; and update.metadata.labels.foo = "bar"; both work without writing old: ... lambdas.

The match selector has also grown up: it now uses ordinary attribute paths (metadata.labels."app.kubernetes.io/name"), searches list elements for a match (e.g. spec.containers.envFrom.secretRef.name = "foo" matches any pod container referencing that secret), and accepts lists of values for OR-matching (namespace = [ "foo" "bar" ]).

Runtime stages (previously postProcess rules inside objectTransforms) have moved to their own nixidy.postProcessors option, environment-wide or per-application, with the same stdin to stdout contract, confirmation prompt, and NIXIDY_POST_PROCESS_APPROVE / NIXIDY_SKIP_POST_PROCESS behaviour as before:

{
  nixidy.postProcessors.encrypt-secrets = {
    match.kind = "SopsSecret";
    runtimeInputs = [ pkgs.sops ];
    command = "sops --encrypt --input-type yaml --output-type yaml /dev/stdin";
  };
}

See the rewritten Object Transforms documentation and the new Post-processing page.

CRD option types now validate your values - #​56

The CRD resource options generators now fold JSON Schema validation keywords into the generated option types: minimum/maximum (inclusive and exclusive), multipleOf, minLength/maxLength, and scalar enum values. Out-of-bounds resource values are rejected at evaluation time by both the file and value backends, so a typo like replicas = 0 against a schema requiring at least 1 fails at build instead of at apply:

error: A definition for option '...' is not of type 'integer (minimum 1)'.

Breaking Changes

  • objectTransforms is now an attrset of transforms instead of a list of rules. The rewrite key is gone; use replace or update instead. Runtime stages moved to the new postProcessors option with command instead of postProcess. Rules run in attribute-name order (env first, then app scope). #​109
  • The post-process multi-document assertion is stricter. A build error is now raised when a post-processor matches only some objects of a multi-document file, a case that was previously undefined. Post-processed files must be single-object. #​102

Improvements

  • Build module split into a pure layout seam + emitters. The monolithic modules/build.nix was restructured into modules/build/ as a functional-core pipeline: a pure layout.nix that turns each application into a list of FileSpec (exposed as the internal config.build.layout), with render.nix, emit-environment.nix and apply.nix consuming it. No public API change, but switch and apply now post-process identical file sets by construction, and an application whose name is overridden no longer fails to build. #​102 @​sini

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [arnarg/nixidy](https://github.com/arnarg/nixidy) | minor | `v0.22.1` → `v0.23.1` | --- ### Release Notes <details> <summary>arnarg/nixidy (arnarg/nixidy)</summary> ### [`v0.23.1`](https://github.com/arnarg/nixidy/releases/tag/v0.23.1) [Compare Source](https://github.com/arnarg/nixidy/compare/v0.23.0...v0.23.1) This is a small bugfix release. #### Bug Fixes - **Function `replace` in `objectTransforms` is now applied instead of wrapped.** The `replace` option's type coercion accepted functions as plain values, so a lambda like `replace = old: old // { ... };` was returned as-is instead of being called with the old object. The coerced type now excludes functions, so function replaces transform the matched object (or part) again, while plain values keep being coerced to `_: value`. [@&#8203;sini](https://github.com/sini) [#&#8203;112](https://github.com/arnarg/nixidy/issues/112) ### [`v0.23.0`](https://github.com/arnarg/nixidy/releases/tag/v0.23.0) [Compare Source](https://github.com/arnarg/nixidy/compare/v0.22.1...v0.23.0) #### New Features ##### Object Transforms, reimagined: transform parts of resources - [@&#8203;mewp](https://github.com/mewp) [#&#8203;109](https://github.com/arnarg/nixidy/issues/109) The object transform mechanism has been completely reworked and is far more powerful now. Instead of a list of rules with a `rewrite` function, `objectTransforms` is an attrset where each transform can act on a whole resource **or on just a part of it**: ```nix { nixidy.objectTransforms = { # Match objects, then update a part of them. fix-store = { match.kind = "ExternalSecret"; update.spec.secretStoreRef = { kind = "ClusterSecretStore"; name = "foo"; }; }; # Target a specific path inside every matched resource. List elements # are iterated, so this rewrites every container in every Deployment: add-tty = { match.kind = "Deployment"; transforms.tty = { path = [ "spec" "template" "spec" "containers" ]; update.tty = true; }; }; # Setting a part to null removes the attribute. drop-foo-label = { path = [ "metadata" "labels" "foo" ]; replace = null; }; }; } ``` Each transform sets exactly one of `replace` (swap the value or the whole object, returning `null` drops it), `update` (recursively merge into the old value), or `transforms` (nested transforms, scoped to what the outer transform matched and nestable arbitrarily deep). Plain values are accepted anywhere a function is, so `replace = { ... };` and `update.metadata.labels.foo = "bar";` both work without writing `old: ...` lambdas. The `match` selector has also grown up: it now uses ordinary attribute paths (`metadata.labels."app.kubernetes.io/name"`), searches list elements for a match (e.g. `spec.containers.envFrom.secretRef.name = "foo"` matches any pod container referencing that secret), and accepts lists of values for OR-matching (`namespace = [ "foo" "bar" ]`). Runtime stages (previously `postProcess` rules inside `objectTransforms`) have moved to their own `nixidy.postProcessors` option, environment-wide or per-application, with the same stdin to stdout contract, confirmation prompt, and `NIXIDY_POST_PROCESS_APPROVE` / `NIXIDY_SKIP_POST_PROCESS` behaviour as before: ```nix { nixidy.postProcessors.encrypt-secrets = { match.kind = "SopsSecret"; runtimeInputs = [ pkgs.sops ]; command = "sops --encrypt --input-type yaml --output-type yaml /dev/stdin"; }; } ``` See the rewritten [Object Transforms](https://nixidy.dev/user_guide/object_transforms/) documentation and the new [Post-processing](https://nixidy.dev/user_guide/postprocessing/) page. ##### CRD option types now validate your values - [#&#8203;56](https://github.com/arnarg/nixidy/issues/56) The CRD resource options generators now fold JSON Schema validation keywords into the generated option types: `minimum`/`maximum` (inclusive and exclusive), `multipleOf`, `minLength`/`maxLength`, and scalar `enum` values. Out-of-bounds resource values are rejected at evaluation time by both the file and value backends, so a typo like `replicas = 0` against a schema requiring at least 1 fails at build instead of at apply: ```sh error: A definition for option '...' is not of type 'integer (minimum 1)'. ``` #### Breaking Changes - **`objectTransforms` is now an attrset of transforms instead of a list of rules.** The `rewrite` key is gone; use `replace` or `update` instead. Runtime stages moved to the new `postProcessors` option with `command` instead of `postProcess`. Rules run in attribute-name order (env first, then app scope). [#&#8203;109](https://github.com/arnarg/nixidy/issues/109) - **The post-process multi-document assertion is stricter.** A build error is now raised when a post-processor matches only some objects of a multi-document file, a case that was previously undefined. Post-processed files must be single-object. [#&#8203;102](https://github.com/arnarg/nixidy/issues/102) #### Improvements - **Build module split into a pure layout seam + emitters.** The monolithic `modules/build.nix` was restructured into `modules/build/` as a functional-core pipeline: a pure `layout.nix` that turns each application into a list of `FileSpec` (exposed as the internal `config.build.layout`), with `render.nix`, `emit-environment.nix` and `apply.nix` consuming it. No public API change, but `switch` and `apply` now post-process identical file sets by construction, and an application whose `name` is overridden no longer fails to build. [#&#8203;102](https://github.com/arnarg/nixidy/issues/102) [@&#8203;sini](https://github.com/sini) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 🔕 **Ignore**: Close this PR and you won't be reminded about this update again. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC43OS4yIiwidXBkYXRlZEluVmVyIjoiNDQuNzkuMiIsInRhcmdldEJyYW5jaCI6Im1haW4iLCJsYWJlbHMiOlsiZGVwZW5kZW5jaWVzIl19-->
chore(deps): update dependency arnarg/nixidy to v0.23.0
Some checks failed
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/switch Pipeline failed
12c6818d8b
clank-bot force-pushed renovate/arnarg-nixidy-0.x from 12c6818d8b
Some checks failed
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/switch Pipeline failed
to 29e1b16478
Some checks failed
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/switch Pipeline failed
2026-10-16 00:00:32 +00:00
Compare
clank-bot changed title from chore(deps): update dependency arnarg/nixidy to v0.23.0 to chore(deps): update dependency arnarg/nixidy to v0.23.1 2026-10-16 00:00:33 +00:00
martin self-assigned this 2026-10-18 16:46:53 +00:00
fix: migrate object transforms to nixidy v0.23
All checks were successful
ci/woodpecker/pr/pr-review Pipeline was successful
ci/woodpecker/pr/switch Pipeline was successful
bdb9cdab2f
martin merged commit 7f3f06f0ef into main 2026-10-18 17:34:54 +00:00
martin deleted branch renovate/arnarg-nixidy-0.x 2026-10-18 17:34:54 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
Personal/cluster!61
No description provided.