How it came to be? Traditionally setting up infrastructure for the code to run (think: servers, network configurations, etc) has been a manual task. People started using SOP (Standard Operating Procedure) in order to mitigate errors and risk (by listing down all the actionable items) but it’s still error-prone. Enter, Infrastructure as code. This is an attempt to abstract the tangible aspects of software (hardware it runs on, configurations and network it uses, etc).

Executing commands remotely and returning results One of the common usage is to log into remote machine and check some process stat to see if some program is running or not. Instead of logging in, executing command and then returning back, we can do it in a single shot by providing the command to be executed as an argument. ssh loguser@$x.x.x "ps -ef | grep kafka" loguser 12214 12213 0 23:47 ?