Skip to content

Register `Squid.DeployWindowsService` as a first-class deployment action type.

Placeholder MINDY.L requested to merge codex/register-windows-service-action into feature/deploy-windows-service

Summary

  • Registered Squid.DeployWindowsService as a first-class deployment action type by adding the action type constant and including it in the canonical ActionTypes.All registration surface.
  • Added the Windows Service deploy property constants in WindowsServiceDeployProperties, covering service identity, executable/arguments, service account, start/desired state, dependencies, and package source/extract behavior.
  • Added the Tentacle OS property constant to SpecialVariables so later handler/runtime checks can read the target OS from the same shared contract.
  • Declared Squid.DeployWindowsService as supported by both Tentacle polling and listening transports, allowing the action type to pass transport capability validation for Windows Tentacle targets.
  • Added focused registration/capability tests to lock the new action type into the platform registry and guard against future drift.

Test plan

  • Unit: WindowsServiceActionRegistrationTests verifies Squid.DeployWindowsService is present in ActionTypes.All and has the expected property constants.
  • Unit: TransportCapabilitiesTests verifies both Tentacle polling and listening transports advertise support for the Windows Service deploy action.
  • Regression: ActionTypesDriftTests included in the targeted run to ensure the new action type stays aligned with the central action type registry.
  • Targeted test run: DOTNET_ROLL_FORWARD=Major dotnet test tests/Squid.UnitTests/Squid.UnitTests.csproj --filter "FullyQualifiedName~WindowsServiceActionRegistrationTests|FullyQualifiedName~TransportCapabilitiesTests|FullyQualifiedName~ActionTypesDriftTests" passed, 15 tests green.

Merge request reports