<# FPS:Metadata:Pro-ServerCIs:ACTIVE #>

# Add all the servers below. A server will use the CICD aspects of the system to pull any new runtime files from the runtime drive of the

# core server associated with the domain. CICD updates can be configured to occur ether upon startup or as part of a scheduled job. A scheduled

# job would be the better option if there is regular data cleanup performed via a poller of sorts. CICD updates are always performed against the

# runtime drive of the source server to the runtime of the server noted in the CICD maintained server configuration. Currently, this file is

# maintained manually, but could be easily be an automated edit.

$global:pro_CIAttributes = @( $global:pro_CIAttributes

# Each server can have only one purpose, but multiple MID servers. Therefore only 1 entry is necessary per on-prem VM.

[PSCustomObject]@{ CIID = "003"; CI = "SVR003"; CITemplate = "ED1_FPS[platform]_003"; RuntimeDrive = "D:"; Type = "Server"; Domain = 'EntDomain01'; SvcAcct = "[UserID]@outlook.com"; Family = "Aloha"; Patch = "P1"; CanConnectToSource = "True"; SourceDrive = "C:\Users\[UserID]\OneDrive" }

### Add additional CICD maintained servers here ###

)

# Sometimes its beneficial to break up the servers to their various domains in additional config file. In the current portfolio, 2 domains

# are used. The following would be a example of separate domain config loads if the decision was made to have 1 per domain.

# . ($global:pro_CI.RuntimeDrive+"\FPS\MetaData\Pro-EntDomain01-ServerCIs.ps1")

# . ($global:pro_CI.RuntimeDrive+"\FPS\MetaData\Pro-EntDomain02-ServerCIs.ps1")