- Adding in links for new post-processors missing
This commit is contained in:
parent
a66d125fc9
commit
38bf53ed84
|
@ -7,7 +7,7 @@ layout: docs
|
||||||
page_title: 'Google Compute Image Exporter'
|
page_title: 'Google Compute Image Exporter'
|
||||||
...
|
...
|
||||||
|
|
||||||
# Google Compoute Image Exporter Post-Processor
|
# Google Compute Image Exporter Post-Processor
|
||||||
|
|
||||||
Type: `googlecompute-export`
|
Type: `googlecompute-export`
|
||||||
|
|
||||||
|
@ -33,15 +33,15 @@ permissions to the GCS `paths`.
|
||||||
|
|
||||||
### Optional
|
### 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.
|
(GCE) image being exported.
|
||||||
|
|
||||||
## Basic Example
|
## 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
|
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
|
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`.
|
`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.
|
`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
|
In order for this example to work, the account associated with `account.json` must
|
||||||
|
|
|
@ -81,7 +81,9 @@
|
||||||
<li><a href="/docs/post-processors/docker-push.html">Docker Push</a></li>
|
<li><a href="/docs/post-processors/docker-push.html">Docker Push</a></li>
|
||||||
<li><a href="/docs/post-processors/docker-save.html">Docker Save</a></li>
|
<li><a href="/docs/post-processors/docker-save.html">Docker Save</a></li>
|
||||||
<li><a href="/docs/post-processors/docker-tag.html">Docker Tag</a></li>
|
<li><a href="/docs/post-processors/docker-tag.html">Docker Tag</a></li>
|
||||||
|
<li><a href="/docs/post-processors/googlecompute-export.html">Google Compute Export</a></li>
|
||||||
<li><a href="/docs/post-processors/shell-local.html">Local Shell</a></li>
|
<li><a href="/docs/post-processors/shell-local.html">Local Shell</a></li>
|
||||||
|
<li><a href="/docs/post-processors/manifest.html">Manifest</a></li>
|
||||||
<li><a href="/docs/post-processors/vagrant.html">Vagrant</a></li>
|
<li><a href="/docs/post-processors/vagrant.html">Vagrant</a></li>
|
||||||
<li><a href="/docs/post-processors/vagrant-cloud.html">Vagrant Cloud</a></li>
|
<li><a href="/docs/post-processors/vagrant-cloud.html">Vagrant Cloud</a></li>
|
||||||
<li><a href="/docs/post-processors/vsphere.html">vSphere</a></li>
|
<li><a href="/docs/post-processors/vsphere.html">vSphere</a></li>
|
||||||
|
|
Loading…
Reference in New Issue