Added gcs destination to init_scripts in databricks_cluster (#1308)

Author: neilbest-db

.devcontainer/Dockerfile

@@ -37,4 +37,6 @@ RUN \
     # # --> Go symbols and outline for go to symbol support and test support 
     && go install github.com/acroca/[email protected] \
     # # --> Static checker
-    && go install honnef.co/go/tools/cmd/[email protected]
+    && go install honnef.co/go/tools/cmd/[email protected] \
+    # # --> TF formatter
+    && go get github.com/katbyte/terrafmt

clusters/clusters_api.go

@@ -186,6 +186,11 @@ type S3StorageInfo struct {
 	CannedACL        string `json:"canned_acl,omitempty"`
 }
 
+// GcsStorageInfo contains the struct for when storing files in GCS
+type GcsStorageInfo struct {
+	Destination string `json:"destination,omitempty" tf:"optional"`
+}
+
 // LocalFileInfo represents a local file on disk, e.g. in a customer's container.
 type LocalFileInfo struct {
 	Destination string `json:"destination,omitempty" tf:"optional"`
@@ -200,6 +205,7 @@ type StorageInfo struct {
 // InitScriptStorageInfo captures the allowed sources of init scripts.
 type InitScriptStorageInfo struct {
 	Dbfs *DbfsStorageInfo `json:"dbfs,omitempty" tf:"group:storage"`
+	Gcs  *GcsStorageInfo  `json:"gcs,omitempty" tf:"group:storage"`
 	S3   *S3StorageInfo   `json:"s3,omitempty" tf:"group:storage"`
 	File *LocalFileInfo   `json:"file,omitempty" tf:"optional"`
 }

docs/resources/cluster.md

@@ -242,7 +242,9 @@ There are a few more advanced attributes for S3 log delivery:
 
 ## init_scripts
 
-You can specify up to 10 different init scripts for the specific cluster. If you want a shell script to run on all clusters and jobs within the same workspace, you should consider [databricks_global_init_script](global_init_script.md).
+To run a particular init script on all clusters within the same workspace, both automated/job and interactive/all-purpose cluster types, please consider the [databricks_global_init_script](global_init_script.md) resource.
+
+It is possible to specify up to 10 different cluster-scoped init scripts per cluster.  Like the `cluster_log_conf` configuration block, init scripts support DBFS and cloud storage locations. 
 
 Example of taking init script from DBFS:
 ```hcl
@@ -263,7 +265,16 @@ init_scripts {
 }
 ```
 
-Like the `cluster_log_conf` configuration block, init scripts support S3 and DBFS locations. In addition, you can also specify a local file as follows:
+Similarly, for an init script stored in GCS:
+```hcl
+init_scripts {
+  gcs {
+    destination = "gs://init-scripts/install-elk.sh"
+  }
+}
+```
+
+ Clusters with [custom Docker containers](https://docs.databricks.com/clusters/custom-containers.html) also allow a local file location for init scripts as follows:
 
 ```hcl
 init_scripts {
@@ -273,8 +284,6 @@ init_scripts {
 }
 ```
 
-Take note that this can only be specified for clusters with [custom Docker containers](https://docs.databricks.com/clusters/custom-containers.html).
-
 ## aws_attributes
 
 `aws_attributes` optional configuration block contains attributes related to [clusters running on Amazon Web Services](https://docs.databricks.com/clusters/configure.html#aws-configurations).

docs/resources/mws_networks.md

@@ -81,7 +81,7 @@ resource "databricks_mws_networks" "this" {
   }
   depends_on = [aws_vpc_endpoint.workspace, aws_vpc_endpoint.relay]
 }
-  ```
+```
 
 ## Modifying networks on running workspaces