|
|
|
|
@ -7,7 +7,7 @@ layout: docs
|
|
|
|
|
page_title: 'Google Compute Image Exporter'
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
# Google Compoute Image Exporter Post-Processor
|
|
|
|
|
# Google Compute Image Exporter Post-Processor
|
|
|
|
|
|
|
|
|
|
Type: `googlecompute-export`
|
|
|
|
|
|
|
|
|
|
@ -33,15 +33,15 @@ permissions to the GCS `paths`.
|
|
|
|
|
|
|
|
|
|
### Optional
|
|
|
|
|
|
|
|
|
|
- `keep_input_artifact` (bool) - If true, do not delete the Google Compute Engine
|
|
|
|
|
- `keep_input_artifact` (bool) - If true, do not delete the Google Compute Engine
|
|
|
|
|
(GCE) image being exported.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
## Basic Example
|
|
|
|
|
|
|
|
|
|
The following example builds a GCE image in the project, `my-project`, with an
|
|
|
|
|
The following example builds a GCE image in the project, `my-project`, with an
|
|
|
|
|
account whose keyfile is `account.json`. After the image build, a temporary VM will
|
|
|
|
|
be created to export the image as a gzipped tarball to
|
|
|
|
|
`gs://mybucket1/path/to/file1.tar.gz` and `gs://mybucket2/path/to/file2.tar.gz`.
|
|
|
|
|
be created to export the image as a gzipped tarball to
|
|
|
|
|
`gs://mybucket1/path/to/file1.tar.gz` and `gs://mybucket2/path/to/file2.tar.gz`.
|
|
|
|
|
`keep_input_artifact` is true, so the GCE image won't be deleted after the export.
|
|
|
|
|
|
|
|
|
|
In order for this example to work, the account associated with `account.json` must
|
|
|
|
|
|