From d4a0541391e0acd519acfd93a061ce97c654d4de Mon Sep 17 00:00:00 2001
From: Luke Van Seters <lukevanseters@gmail.com>
Date: Tue, 2 Nov 2021 14:31:47 -0400
Subject: [PATCH] Add mev exec to execute a command on the inspect pod

---
 README.md | 4 ++--
 mev       | 4 ++++
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 9e1f588..9228ae0 100644
--- a/README.md
+++ b/README.md
@@ -54,7 +54,7 @@ Press "space" to see a browser of the services starting up.
 On first startup, you'll need to apply database migrations with:
 
 ```
-kubectl exec deploy/mev-inspect -- alembic upgrade head
+./mev exec alembic upgrade head
 ```
 
 ## Usage
@@ -181,7 +181,7 @@ tilt up
 And rerun migrations to create the tables again:
 
 ```
-kubectl exec deploy/mev-inspect -- alembic upgrade head
+./mev exec alembic upgrade head
 ```
 
 ### I was using the docker-compose setup and want to switch to kube, now what?
diff --git a/mev b/mev
index 45b2aa6..ef520d2 100755
--- a/mev
+++ b/mev
@@ -56,6 +56,10 @@ case "$1" in
       echo "Fetching block $block_number"
       kubectl exec -ti deploy/mev-inspect -- poetry run fetch-block $block_number
   ;;
+  exec)
+        shift
+        kubectl exec -ti deploy/mev-inspect -- $@
+  ;;
   *)
 	echo "Usage: "$1" {db|backfill|inspect|test}"
 	exit 1