Joseph Doherty
7b0b9c7365
Solution + 23 src projects + 26 test projects renamed; folders, csproj, namespaces, and ScadaLinkDbContext/ScadaBridgeDbContext class updated. ActorSystem "scadalink" → "scadabridge", Akka seed-node URLs migrated. SQL roles/logins, LDAP domains, CLI command name, and CLI config dir (~/.scadalink → ~/.scadabridge) also renamed. Build green; 5 Host.Tests fail awaiting SQL login rename in next commit. Pre-existing StaleTagMonitor timing flakes unchanged. Rename script committed at tools/rename-to-scadabridge.sh.
21 lines
920 B
C#
21 lines
920 B
C#
namespace ZB.MOM.WW.ScadaBridge.DeploymentManager;
|
|
|
|
/// <summary>
|
|
/// Configuration options for the central-side Deployment Manager.
|
|
/// </summary>
|
|
public class DeploymentManagerOptions
|
|
{
|
|
/// <summary>
|
|
/// WP-6: Timeout for a lifecycle command round-trip (disable, enable, delete).
|
|
/// Applied as a linked-CTS deadline in <c>DeploymentService</c> so a hung or
|
|
/// unreachable site does not hold the per-instance operation lock indefinitely.
|
|
/// </summary>
|
|
public TimeSpan LifecycleCommandTimeout { get; set; } = TimeSpan.FromSeconds(30);
|
|
|
|
/// <summary>WP-7: Timeout per site for system-wide artifact deployment.</summary>
|
|
public TimeSpan ArtifactDeploymentTimeoutPerSite { get; set; } = TimeSpan.FromSeconds(120);
|
|
|
|
/// <summary>WP-3: Timeout for acquiring an operation lock on an instance.</summary>
|
|
public TimeSpan OperationLockTimeout { get; set; } = TimeSpan.FromSeconds(5);
|
|
}
|