waagent: 2.12.0.4 -> 2.13.1.1

[codgician]

Things done

• [package] Bumped waagent to 2.13.1.1
• [module] Changed AutoUpdate.Enabled to AutoUpdate.UpdateToLatestVersion as the former one is marked as legacy according to: official FAQ. Migration is not needed because the module already takes arbitrary config value, and the former option is still being accepted by waagent.

• 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.

[codgician]

@NixOS/nixpkgs-merge-bot merge

[nixpkgs-merge-bot]

@codgician merge not permitted (#305350):
nixos/modules/virtualisation/waagent.nix is not in pkgs/by-name/

[pbsds]

what happens if both Enable and UpdateToLatestVersion are set? One risk is that users have set Enable, then this PR will merge a UpdateToLatestVersion into their config as well.

[codgician]

what happens if both Enable and UpdateToLatestVersion are set? One risk is that users have set Enable, then this PR will merge a UpdateToLatestVersion into their config as well.

Referring the example in FAQ, when AutoUpdate.Enable=y is set, the behavior would be the same regardless of AutoUpdate.UpdateToLatestVersion value for compatibility.

[pbsds]

Man what a detailed FAQ for this exact question, thank you