2017-03-21 23:01:58 +01:00
|
|
|
---
|
2017-04-03 19:53:38 +02:00
|
|
|
layout: "enterprise"
|
2017-04-07 06:00:42 +02:00
|
|
|
page_title: "Packer Artifacts - Terraform Enterprise"
|
2017-04-03 19:53:38 +02:00
|
|
|
sidebar_current: "docs-enterprise-packerartifacts"
|
2017-03-22 18:31:44 +01:00
|
|
|
description: |-
|
|
|
|
|
Packer creates and uploads artifacts to Terraform Enterprise.
|
2017-03-21 23:01:58 +01:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# About Packer and Artifacts
|
|
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
Packer creates and uploads artifacts to Terraform Enterprise. This is done
|
|
|
|
|
with the [post-processor](https://packer.io/docs/post-processors/atlas.html).
|
2017-03-21 23:01:58 +01:00
|
|
|
|
2017-04-07 06:00:42 +02:00
|
|
|
Artifacts can then be used to deploy services or access via Vagrant. Artifacts
|
|
|
|
|
are generic, but can be of varying types. These types define different behavior
|
|
|
|
|
within Terraform Enterprise.
|
2017-03-21 23:01:58 +01:00
|
|
|
|
2017-04-07 06:00:42 +02:00
|
|
|
For uploading artifacts `artifact_type` can be set to any unique identifier,
|
|
|
|
|
however, the following are recommended for consistency.
|
2017-03-21 23:01:58 +01:00
|
|
|
|
|
|
|
|
- `amazon.image`
|
|
|
|
|
- `azure.image`
|
|
|
|
|
- `digitalocean.image`
|
|
|
|
|
- `docker.image`
|
|
|
|
|
- `google.image`
|
|
|
|
|
- `openstack.image`
|
|
|
|
|
- `parallels.image`
|
|
|
|
|
- `qemu.image`
|
|
|
|
|
- `virtualbox.image`
|
|
|
|
|
- `vmware.image`
|
|
|
|
|
- `custom.image`
|
|
|
|
|
- `application.archive`
|
|
|
|
|
- `vagrant.box`
|
|
|
|
|
|
2017-03-22 18:31:44 +01:00
|
|
|
Packer can create artifacts when running in Terraform Enterprise or locally.
|
2017-04-07 06:00:42 +02:00
|
|
|
This is possible due to the post-processors use of the public artifact API to
|
|
|
|
|
store the artifacts.
|
2017-03-21 23:01:58 +01:00
|
|
|
|
2017-04-07 06:00:42 +02:00
|
|
|
You can read more about artifacts and their use in the
|
|
|
|
|
[Terraform section](/docs/enterprise/) of the documentation.
|
