Change how the EFS File System is handled

For the AWS backend.

Bring it in to the Terraform configuration for the backend, where
previously only the id was known. Also, alter the provisioning so that
it can handle an empty EFS file system.

This reduces the amount of manual setup required for AWS.

2 files changed, 7 insertions, 2 deletions

diff --git a/db/migrate/20180603120426_remove_efs_file_system_id_from_backends_terraform_aws.rb b/db/migrate/20180603120426_remove_efs_file_system_id_from_backends_terraform_aws.rb
new file mode 100644
index 0000000..25abfb5
--- /dev/null
+++ b/db/migrate/20180603120426_remove_efs_file_system_id_from_backends_terraform_aws.rb
@@ -0,0 +1,5 @@
+class RemoveEfsFileSystemIdFromBackendsTerraformAws < ActiveRecord::Migration[5.1]
+  def change
+    remove_column :terraform_aws_backends, :efs_file_system_id, :string
+  end
+end
diff --git a/db/structure.sql b/db/structure.sql
index 9e03d7d..36c6abb 100644
--- a/db/structure.sql
+++ b/db/structure.sql
@@ -256,7 +256,6 @@ 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,
-    efs_file_system_id character varying NOT NULL,
     vpc_id character varying NOT NULL
 );
 
@@ -660,6 +659,7 @@ INSERT INTO "schema_migrations" (version) VALUES
 ('20180530191341'),
 ('20180530192706'),
 ('20180601153537'),
-('20180601182655');
+('20180601182655'),
+('20180603120426');