Cargo.toml

@@ -2,3 +2,6 @@
 name = "confirm-before"
 version = "0.1.0"
 authors = ["Marcelo Boeira <me@marceloboeira.com>"]
+
+[dependencies]
+termion = "1"

README.md

@@ -4,6 +4,13 @@
   <p align="center">Sanity check for your shell commands<p>
 </p>
 
+## Installing
+
+```
+brew tap marceloboeira/formulas
+brew install marceloboeira/formulas/confirm-before
+```
+
 ## Motivation
 
 I have recently started working with a lot of DevOps CLIs that interact with staging and production servers.
@@ -27,3 +34,23 @@ Then, ...
 $ kp apply -F *
 Are you sure? (y/n)
 ```
+
+## Future
+
+I might create other sanity check levels/modes:
+
+```
+$ alias dangerous=`confirm-before --math dangerous --production`
+$ dangerous get foo
+How much is 19 - 3?
+```
+
+Conditionals, because it can become very annoying to confirm read-only commands...
+
+```
+$ alias dangerous=`confirm-before --matching delete|d|rm|apply dangerous --production`
+$ dangerous delete foo
+Are you sure? (y/n)
+...
+$ dangerous get foo -> doesn't match the regexp
+```

src/main.rs

@@ -1,25 +1,34 @@
-use std::io;
+use std::io::{self, Write};
 use std::env;
-use std::process::Command;
+use std::process::{Command, Stdio};
+
+extern crate termion;
 
 fn main() {
+    // Use the tty to prevent writing to stdout
+    let mut tty = termion::get_tty().unwrap();
+
     // Collect the command from the input
     let args: Vec<String> = env::args().collect();
     let command: String = args.iter()
                               .skip(1)
                               .fold(String::new(), |acc, item| { acc + " " + item });
 
-    // Confirm
-    println!("Are you sure? (y/n)");
+    // Confirm message
+    writeln!(tty, "Are you sure? (y/n)").unwrap();
+    tty.flush().unwrap();
+
     let mut answer = String::new();
     match io::stdin().read_line(&mut answer) {
         Ok(_) => {
             if answer == "y\n" {
                 Command::new("sh")
                     .arg("-c")
                     .arg(command)
-                    .spawn()
-                    .expect("foo");
+                    .stdout(Stdio::inherit())
+                    .stderr(Stdio::inherit())
+                    .output()
+                    .expect("Something went wrong");
             }
             else {
                 println!("Okay, not running!")

tests/integration.sh

@@ -3,13 +3,13 @@
 printf "Running 'confirm-before' tests: \n"
 
 printf "  when a 'y' is given it runs the command - "
-echo "y\n" | confirm-before echo result | grep -q result; if [ $? != 0 ]; then echo "FAIL"; exit 1; else echo "PASS"; fi
+echo "y\n" | confirm-before 'echo result' | grep -q result; if [ $? != 0 ]; then echo "FAIL"; exit 1; else echo "PASS"; fi
 
 printf "  when a 'n' is given it does not run the command - "
-echo "n\n" | confirm-before echo result | grep -q result; if [ $? != 0 ]; then echo "PASS"; else echo "FAIL"; exit 1; fi
+echo "n\n" | confirm-before 'echo result' | grep -q result; if [ $? != 0 ]; then echo "PASS"; else echo "FAIL"; exit 1; fi
 
-printf "  when a 'p' is given it does not run the command - "
-echo "p\n" | confirm-before echo result | grep -q result; if [ $? != 0 ]; then echo "PASS"; else echo "FAIL"; exit 1; fi
+printf "  when a complex command is given it gets the output - "
+echo "y\n" | confirm-before 'cat ./tests/resource.txt' | grep -q content; if [ $? != 0 ]; then echo "FAIL"; exit 1; else echo "PASS"; fi
 
-printf "  when a complex command is given - "
-echo "y\n" | confirm-before cat ./tests/resource.txt | grep -q content; if [ $? != 0 ]; then echo "FAIL"; exit 1; else echo "PASS"; fi
+printf "  when a slow command is given it waits for it to finish - "
+echo "y\n" | confirm-before 'sleep 1; echo content' | grep -q content; if [ $? != 0 ]; then echo "FAIL"; exit 1; else echo "PASS"; fi