databricks_mount S3: Use zone_id:"auto"

[marekbrysa]

This way Databricks will automatically choose the zone in the given region where the default instance type can be created.

Resolves #1756.

[codecov-commenter]

Codecov Report

Merging #1932 (875b7c5) into master (fd1f11a) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #1932   +/-   ##
=======================================
  Coverage   90.19%   90.19%           
=======================================
  Files         146      146           
  Lines       11843    11844    +1     
=======================================
+ Hits        10682    10683    +1     
  Misses        748      748           
  Partials      413      413           

Impacted Files	Coverage Δ
storage/aws_s3_mount.go	87.65% <100.00%> (+0.15%)	⬆️

[alexott]

@marekbrysa aws_s3_mount is deprecated in favor of databricks_mount and will be removed in the next major version - we won't make any changes in aws_s3_mount

[marekbrysa]

@alexott please correct me if I'm wrong, but I think my change will get used with databricks_mount like this:

terraform-provider-databricks/storage/resource_mount.go

Line 30 in a39cf20

if err := preprocessS3MountGeneric(ctx, scm, d, m); err != nil {

terraform-provider-databricks/storage/s3.go

Line 78 in a39cf20

return mountS3ViaProfileAndSetClusterID(clustersAPI, instanceProfile, d)

terraform-provider-databricks/storage/s3.go

Line 85 in a39cf20

cluster, err := GetOrCreateMountingClusterWithInstanceProfile(clustersAPI, instanceProfile)

terraform-provider-databricks/storage/aws_s3_mount.go

Line 137 in a39cf20

Availability: "SPOT",

So I am changing the code related to databricks_mount?