pulumi: 3.122.0 -> 3.152.0

[tie]

This PR updates Pulumi to the latest version (pulumi/pulumi@v3.122.0...v3.152.0) and fixes cross-compilation.

Refactor and version bumps for pulumiPackages will be submitted in a follow up PRs.

Old description

https://github.com/NixOS/nixpkgs/compare/master...tie:nixpkgs:pulumi-packages-bump?expand=1

This PR updates Pulumi to the latest version (pulumi/pulumi@v3.122.0...v3.152.0), along with significant refactor and updates for pulumiPackages. This PR fixes cross-compilation for Pulumi packages and uses correct Python package set for SDKs. All packages now have passthru.updateScript to ease updates in the future.

We also remove mkPulumiPackage helper function and use buildGoModule directly. While Pulumi packages have similar architecture, there are minor differences in build logic that would otherwise require a lot of special cases. Note that mkPulumiPackage was never exposed so it is a backwards compatible change.

There is an existing PR #352221, but it’s already outdated and seems to be unfinished (e.g. some packages fail to build).

Note that Pulumi requires protobuf4 for Python packages. See also #351751 (comment)

Build all Pulumi packages, SDKs and tests with:

nix build --impure --expr 'with import ./. {
  config.allowAliases = false;
  overlays = [
    (_: prev: {
      pythonPackagesExtensions = prev.pythonPackagesExtensions ++ [
        (final: _: {
          protobuf = final.protobuf4;
        })
      ];
    })
  ];
};
linkFarmFromDrvs "pulumi-packages" (
  lib.concatLists (
    lib.mapAttrsToList (
      _: p:
      lib.optionals (lib.isDerivation p) (
        [ p ] ++ lib.attrValues (p.sdks or { }) ++ lib.attrValues (p.tests or { })
      )
    ) (pulumiPackages // { inherit pulumi; })
  )
)'

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[wolfgangwalther]

The first commit is really hard to review, because so many different changes are in one commit. I see:

• addition of maintainer
• refactors
• version update

It would be good to split things up into multiple commits, to create smaller diffs.

[tie]

@wolfgangwalther, I’ve recreated commit history from the final revision, so this is hopefully easier to review commit-by-commit.

[wolfgangwalther]

I looked through the first 10 or so commits and then suddenly there were new packages introduced etc...

This PR seriously needs to be split up in general. 3k lines of code is too much to review - and the PR title also doesn't match anymore. This is not an update... this is rebuilding the whole pulumi package set from scratch.

I suggest you start with a first PR which just adds you as maintainer and does all kinds of modernization, ideally pure refactors - those will already get rid of quite some lines and are easy to review, because you won't have any rebuilds. This could also contain the moves to pkgs/by-name etc.

Then the next step would be everything that is required for the version bump (s).

And then something to improve the infrastructure around the package set, all the helpers etc.

And then one or more PRs to introduce new packages.

Or some other split entirely - but 3k lines is a lot at once.

[wolfgangwalther]

Most changes to the pulumi-langauge-xxx files look unrelated to the actual update and more like refactors.

[tie]

These changes are small cleanups, so I think we can bundle them with the update. I’ve also split them into separate commits in the latest revision.

[tie]

@wolfgangwalther, updated the PR to only include version bump for pulumi package. I’ll submit all other changes in follow up PRs.