Missing engine in gcs configuration

[TarjinderSingh]

I was running a WARP pipeline by the Broad GATK team, and I keep hitting the following error:

Could not build the path "xxx". It may refer to a filesystem not supported by this instance of Cromwell. Supported filesystems are: HTTP, MacOSXFileSystem. Failures: 
HTTP: xxx does not have an http or https scheme (IllegalArgumentException)

I dug through the different gcs backend parameters and found that the pipeline was looking for an "engine" parameter. After adding in the following snippet to backend-file, I was able to get caper and the WARP pipeline to work. Would it be possible to add the engine to caper's default configuration?

engine {
  filesystems {
    gcs {
      auth = "application-default"
      project = "daly-neale-sczmeta"
    }
    local {}
  }
}

[leepc12]

Fixed in v2.2.2. Please re-open if the problem persists.