The Deployment Failed. The Resources Are Still Running.
The deployment reaches the configuration stage and stops.
The network exists. The virtual machine exists. Configuration did not finish, and the health check never ran. The pipeline is red, but the provider console shows resources that are still active.
Both views are technically correct. The command failed. The infrastructure also changed.
The problem starts when automation treats the first fact as if it proves the opposite of the second. A nonzero exit code describes a process outcome. It does not describe the complete state of several remote systems after that process ends.
A Failed Command Is Not a Rollback
Infrastructure workflows often present one action to the operator while making many separate calls underneath it. A deployment may create a network, reserve an address, create a virtual machine, wait for access, configure the operating system, and run service probes.
Those calls do not become one atomic transaction because one command...
Copyright of this story solely belongs to hackernoon.com. To see the full text click HERE
