2017-03-16 20:42:33 +01:00
|
|
|
---
|
2017-04-03 19:53:38 +02:00
|
|
|
layout: "enterprise"
|
2017-03-17 22:34:04 +01:00
|
|
|
page_title: "Terraform Artifacts"
|
2017-03-23 20:28:10 +01:00
|
|
|
sidebar_current: "docs-enterprise-artifacts"
|
2017-03-17 22:34:04 +01:00
|
|
|
description: |-
|
|
|
|
Terraform Enterprise can be used to store artifacts for use by Terraform. Typically, artifacts are stored with Packer.
|
2017-03-16 20:42:33 +01:00
|
|
|
---
|
|
|
|
|
2017-03-20 19:44:03 +01:00
|
|
|
# About Terraform Artifacts
|
2017-03-16 20:42:33 +01:00
|
|
|
|
2017-03-17 22:34:04 +01:00
|
|
|
Terraform Enterprise can be used to store artifacts for use by Terraform. Typically,
|
|
|
|
artifacts are [stored with Packer](https://packer.io/docs).
|
2017-03-16 20:42:33 +01:00
|
|
|
|
2017-03-17 22:34:04 +01:00
|
|
|
Artifacts can be used in to deploy and manage images
|
2017-03-16 20:42:33 +01:00
|
|
|
of configuration. Artifacts are generic, but can be of varying types
|
|
|
|
like `amazon.image`. See the Packer [`artifact_type`](https://packer.io/docs/post-processors/atlas.html#artifact_type)
|
|
|
|
docs for more information.
|
|
|
|
|
2017-03-17 22:34:04 +01:00
|
|
|
Packer can create artifacts both while running in and out of Terraform Enterprise
|
2017-03-16 20:42:33 +01:00
|
|
|
network. This is possible due to the post-processors use of the public
|
2017-03-17 22:34:04 +01:00
|
|
|
artifact API to store the artifacts.
|