Is your feature request related to a problem? Please describe.

When developers try to build a private static web page(built by reg-suit) on GCP, it is more convenient to upload html/img/js files to GCS without gzip compression by reg-publish-gcs-plugin for the following reasons.

• The simple solution for delivering files to limited users is building nginx on Cloud Run mounted GCS and enabling IAP for the Cloud Run service
  • GCS volume mount
  • 4. Serve a static website
• GCS mount uses gcsfuse in the background. This tool has the constraint that the extensions of files compressed by gzip are not .gz(File transcoding). If extensions of the files compressed by gzip are .gz, we can use gzip_static_module on nginx, but it isn't. So, developers have to elaborately build the delivery system.
  • i.e., reg-publish-gcs-plugin uploads index.html with gzip compression to GCS, and nginx delivers the index.html file without the response header Content-Encoding: gzip, then the client displays the compressed index.html file without decompressing. As a result, the users can't read the page.

Describe the solution you'd like

The solution to the problem is that developers can select that reg-publish-gcs-plugin uploads files with or without gzip compression.