Proxy is broken during cloning

[karthik-murugan-hpe]

I've been testing WAL-E/G backup and restore with AWS S3 bucket.

My cluster is behind a proxy, so I configured https_proxy in its manifest. This worked well for the backup and S3 bucket gets populated with base backup.

However while trying to create a cluster by cloning from this S3 bucket, it ends up in connection error after 10 mins or so.

Apparently this code , which populates the env variables ends up prefixing ***_proxy variables with CLONE_.

Workaround is to add an env variable CLONE_https_proxy, so that this code populates it to the restore process.