Make it hard to use the prod state on accident (SumoLogic#22)

* make local state the default

* remove trailing spaces

* re-enable apply

* move all remote-state declarations into the .drone.yml

* remove renaming step

* remove newline

Co-authored-by: Marcin Suterski <msuterski@users.noreply.github.com>

.drone.yml

@@ -21,6 +21,9 @@ steps:
         - plan
       init_options:
         lock-timeout: 5m
+        backend-config:
+          - "bucket=remote-state"
+          - "prefix=nytimes/dv-sumologic"
     environment:
       SUMOLOGIC_ACCESSID:
         from_secret: access_id
@@ -40,6 +43,9 @@ steps:
         - apply
       init_options:
         lock-timeout: 5m
+        backend-config:
+          - "bucket=remote-state"
+          - "prefix=nytimes/dv-sumologic"
     environment:
       SUMOLOGIC_ACCESSID:
         from_secret: access_id

terraform/remote-state.tf

@@ -1,6 +1,7 @@
+# Be careful making changes in this file -- you can accidentally find yourself
+# working with the live production state file.
+# Please reach out in #delivery-engineering if you'd like help working with this.
+
 terraform {
-  backend "gcs" {
-    bucket = "remote-state"
-    prefix = "nytimes/dv-sumologic"
-  }
+  backend "gcs" {}
 }