Fix problem with 'restarted' state not restarting the apppool when it is in running state (#1451)

* Fix problem with 'restarted' state not restarting the apppool when it is in running state

* Implemeting code review comments

Comment from previous commit “You basically want to start the pool if
it's stopped and requested state is started or restarted, otherwise if
requested state is restarted, restart it.” This commit implements the
behavior stated in the PR comment
pull/18777/head
Nicolas Landais 9 years ago committed by Matt Clay
parent d0ada049f2
commit e93f7241be

@ -90,10 +90,18 @@ try {
Stop-WebAppPool -Name $name -ErrorAction Stop Stop-WebAppPool -Name $name -ErrorAction Stop
$result.changed = $TRUE $result.changed = $TRUE
} }
if ((($state -eq 'started') -and ($pool.State -eq 'Stopped')) -or ($state -eq 'restarted')) { if ((($state -eq 'started') -and ($pool.State -eq 'Stopped'))) {
Start-WebAppPool -Name $name -ErrorAction Stop Start-WebAppPool -Name $name -ErrorAction Stop
$result.changed = $TRUE $result.changed = $TRUE
} }
if ($state -eq 'restarted') {
switch ($pool.State)
{
'Stopped' { Start-WebAppPool -Name $name -ErrorAction Stop }
default { Restart-WebAppPool -Name $name -ErrorAction Stop }
}
$result.changed = $TRUE
}
} }
} catch { } catch {
Fail-Json $result $_.Exception.Message Fail-Json $result $_.Exception.Message

Loading…
Cancel
Save