Handle SSH keys via the database

This makes it more explicit, and works around Terraform being
unpredictable when dealing with SSH agents.

2 files changed, 11 insertions, 2 deletions

diff --git a/db/migrate/20180623083735_add_ssh_key_fields_to_terraform_aws_backends.rb b/db/migrate/20180623083735_add_ssh_key_fields_to_terraform_aws_backends.rb
new file mode 100644
index 0000000..2a93530
--- /dev/null
+++ b/db/migrate/20180623083735_add_ssh_key_fields_to_terraform_aws_backends.rb
@@ -0,0 +1,6 @@
+class AddSshKeyFieldsToTerraformAwsBackends < ActiveRecord::Migration[5.1]
+  def change
+    add_column :terraform_aws_backends, :ssh_public_key, :string
+    add_column :terraform_aws_backends, :ssh_private_key, :string
+  end
+end
diff --git a/db/structure.sql b/db/structure.sql
index 342e36c..f766762 100644
--- a/db/structure.sql
+++ b/db/structure.sql
@@ -432,7 +432,9 @@ CREATE TABLE public.terraform_aws_backends (
     updated_at timestamp without time zone NOT NULL,
     domain character varying,
     route_53_zone_id character varying NOT NULL,
-    vpc_id character varying NOT NULL
+    vpc_id character varying NOT NULL,
+    ssh_public_key character varying,
+    ssh_private_key character varying
 );
 
 
@@ -874,6 +876,7 @@ INSERT INTO "schema_migrations" (version) VALUES
 ('20180601182655'),
 ('20180603120426'),
 ('20180621065525'),
-('20180621220505');
+('20180621220505'),
+('20180623083735');