Added all TFE artifact files

This commit is contained in:
Chris Riley 2017-03-17 14:34:04 -07:00 committed by Seth Vargo
parent d7bea2aab4
commit 643ac35bc3
No known key found for this signature in database
GPG Key ID: C921994F9C27E0FF
9 changed files with 113 additions and 284 deletions

View File

@ -1,13 +1,18 @@
---
title: "Atlas Artifact Provider"
layout: "artifacts"
page_title: "Artifact Provider"
sidebar_current: "docs-enterprise-Provider"
description: |-
Terraform has a provider for managing Atlas artifacts called `atlas_artifact`.
---
# Atlas Artifact Provider
Terraform has a [provider](https://terraform.io/docs/providers/index.html) for managing Atlas artifacts called `atlas_artifact`.
# Artifact Provider
This is used to make data stored in Atlas Artifacts available to
Terraform has a [provider](https://terraform.io/docs/providers/index.html) for managing Terraform Enterprise artifacts called `atlas_artifact`.
This is used to make data stored in Artifacts available to
Terraform for interpolation. In the following example, an artifact
is defined and references an AMI ID stored in Atlas.
is defined and references an AMI ID stored in Terraform Enterprise.
provider "atlas" {
# You can also set the atlas token by exporting

View File

@ -1,9 +1,14 @@
---
title: "Creating AMI Artifacts with Packer and Atlas"
layout: "artifacts"
page_title: "Creating AMI Artifacts"
sidebar_current: "docs-enterprise-amis"
description: |-
Creating AMI Artifacts with Packer.
---
# Creating AMI Artifacts with Packer and Atlas
# Creating AMI Artifacts with Packer and Terraform Enterprise
Currently, the best way to create AWS AMI artifacts is with Packer.
We detail how to do this in the [Packer section of the documentation](/help/packer/artifacts/creating-amis).
We detail how to do this in the [Packer section of the documentation](https://atlas.hashicorp.com/help/packer/artifacts/creating-amis).

View File

@ -1,18 +1,21 @@
---
title: "About Terraform Artifacts in Atlas"
layout: "artifacts"
page_title: "Terraform Artifacts"
sidebar_current: "docs-enterprise-artifact"
description: |-
Terraform Enterprise can be used to store artifacts for use by Terraform. Typically, artifacts are stored with Packer.
---
# About Terraform Artifacts in Atlas
Atlas can be used to store artifacts for use by Terraform. Typically,
artifacts are [stored with Packer](/help/packer/artifacts).
Terraform Enterprise can be used to store artifacts for use by Terraform. Typically,
artifacts are [stored with Packer](https://packer.io/docs).
Artifacts can be used in Atlas to deploy and manage images
Artifacts can be used in to deploy and manage images
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.
Packer can create artifacts both while running in Atlas and out of Atlas'
Packer can create artifacts both while running in and out of Terraform Enterprise
network. This is possible due to the post-processors use of the public
artifact API to store the artifacts.

View File

@ -1,10 +1,14 @@
---
title: "Managing Artifact Versions"
layout: "artifacts"
page_title: "Managing Artifact Versions"
sidebar_current: "docs-enterprise-Provider"
description: |-
Artifacts are versioned and assigned a version number, here is how to manage the versions.
---
# Managing Artifact Versions
Artifacts stored in Atlas are versioned and assigned a version number.
Artifacts stored in Terraform Enterprise are versioned and assigned a version number.
Versions are useful to roll back, audit and deploy images specific versions
of images to certain environments in a targeted way.
@ -47,8 +51,8 @@ This will use version 7 of the `web-worker` artifact.
### Pinning Artifacts to Specific Builds
Artifacts can also be pinned to an Atlas build number. This is only
possible if Atlas was used to build the artifact with Packer.
Artifacts can also be pinned to an Terraform build number. This is only
possible if Terraform Enterprise was used to build the artifact with Packer.
resource "atlas_artifact" "web-worker" {
name = "%{DEFAULT_USERNAME}/web-worker"
@ -57,5 +61,5 @@ possible if Atlas was used to build the artifact with Packer.
}
It's recommended to use versions, instead of builds, as it will
be easier to track within Atlas and when building outside of the Atlas
be easier to track when building outside of the Terraform Enterprise
environment.

View File

@ -1,14 +1,17 @@
---
title: "Git Integration"
layout: "vcs"
page_title: "Git Integration"
sidebar_current: "docs-enterprise-vcs"
description: |-
Git repositories can be integrated with Terraform Enterprise by using push command.
---
# Git Integation
Git repositories can be integrated with Atlas by using
Git repositories can be integrated with Terraform Enterprise by using
[`terraform push`](https://www.terraform.io/docs/commands/push.html) to import
Terraform configuration when changes are committed. When Terraform
configuration is imported using `terraform push` a plan is automatically queued
in Atlas.
configuration is imported using `terraform push` a plan is automatically queued.
_**Note:** This integration is for Git repositories **not** hosted on GitHub.
For repositories on GitHub, there is native [GitHub Integration](/help/terraform/vcs/github).
@ -36,7 +39,7 @@ repository, set the necessary variables, and ensure the script is executable.
```
#!/bin/bash
#
# An example hook script to push Terraform configuration to Atlas.
# An example hook script to push Terraform configuration to Terraform Enterprise.
#
# Set the following variables for your project:
# - ENV_NAME - your Atlas environment name (e.g. org/env)

View File

@ -1,15 +1,19 @@
---
title: "Integration with Version Control Software"
layout: "vcs"
page_title: "Integration with Version Control Software"
sidebar_current: "docs-enterprise-artifact"
description: |-
Terraform Enterprise can integrate with version control software Git and GitHub.
---
# Integration with Version Control Software
Atlas can integrate with your version control software to automatically execute
Terraform Enterprise can integrate with your version control software to automatically execute
Terraform with your latest Terraform configuration as you commit changes to
source control.
Different capabilities within Atlas are available depending on the integration
Different capabilities within Terraform Enterprise are available depending on the integration
in use. The available integration options are below.
- [Git](/help/terraform/vcs/git)
- [GitHub](/help/terraform/vcs/github)
- [Git](/docs/enterprise/vcs/git)
- [GitHub](/docs/enterprise/vcs/github)

View File

@ -0,0 +1,28 @@
<% wrap_layout :inner do %>
<% content_for :sidebar do %>
<div class="docs-sidebar hidden-print affix-top" role="complementary">
<ul class="nav docs-sidenav">
<li>
<a href="/docs/enterprise/index.html">&laquo; Terraform Enterprise</a>
</li>
<li<%= sidebar_current(/^docs-enterprise-artifact-/) %>>
<a href="/docs/enterprise/artifact/index.html">Artifact</a>
<ul class="nav nav-visible">
<li<%= sidebar_current("docs-enterprise-artifact-provider") %>>
<a href="/docs/enterprise/artifacts/artifact-provider.html">Artifact Provider</a>
</li>
<li<%= sidebar_current("docs-enterprise-artifact-versions") %>>
<a href="/docs/enterprise/artifacts/managing-versions.html">Managing Versions</a>
</li>
<li<%= sidebar_current("docs-enterprise-artifact-ami") %>>
<a href="/docs/enterprise/artifacts/creating-amis.html">Creating AMI Artifacts</a>
</li>
</ul>
</li>
</ul>
</div>
<% end %>
<%= yield %>
<% end %>

View File

@ -550,264 +550,19 @@
<li<%= sidebar_current("docs-enterprise-runs") %>>
<a href="/docs/enterprise/runs/index.html">Runs</a>
</li>
<ul>
<li<%= sidebar_current("docs-enterprise-runs-starting") %>>
<a href="/docs/enterprise/runs/starting.html">Starting Runs</a>
</li>
</ul>
<li<%= sidebar_current("docs-enterprise-state") %>>
<a href="/docs/enterprise/state/index.html">State</a>
</li>
<li<%= sidebar_current("docs-enterprise-artifact") %>>
<a href="/docs/enterprise/artifacts/index.html">Artifacts</a>
</li>
<li<%= sidebar_current("docs-enterprise-vcs") %>>
<a href="/docs/enterprise/vcs/index.html">VCS Integration</a>
</li>
</ul>
</li>
</ul>
<% end %>
<%= yield %>
=======
<li<%= sidebar_current("docs-providers-nomad") %>>
<a href="/docs/providers/nomad/index.html">Nomad</a>
</li>
<li<%= sidebar_current("docs-providers-ns1") %>>
<a href="/docs/providers/ns1/index.html">NS1</a>
</li>
<li<%= sidebar_current("docs-providers-azurerm") %>>
<a href="/docs/providers/azurerm/index.html">Microsoft Azure</a>
</li>
<li<%= sidebar_current("docs-providers-azurerm") %>>
<a href="/docs/providers/azure/index.html">Microsoft Azure (Legacy ASM)</a>
</li>
<li<%= sidebar_current("docs-providers-mysql") %>>
<a href="/docs/providers/mysql/index.html">MySQL</a>
</li>
<li<%= sidebar_current("docs-providers-openstack") %>>
<a href="/docs/providers/openstack/index.html">OpenStack</a>
</li>
<li<%= sidebar_current("docs-providers-opsgenie") %>>
<a href="/docs/providers/opsgenie/index.html">OpsGenie</a>
</li>
<li<%= sidebar_current("docs-providers-packet") %>>
<a href="/docs/providers/packet/index.html">Packet</a>
</li>
<li<%= sidebar_current("docs-providers-pagerduty") %>>
<a href="/docs/providers/pagerduty/index.html">PagerDuty</a>
</li>
<li<%= sidebar_current("docs-providers-postgresql") %>>
<a href="/docs/providers/postgresql/index.html">PostgreSQL</a>
</li>
<li<%= sidebar_current("docs-providers-powerdns") %>>
<a href="/docs/providers/powerdns/index.html">PowerDNS</a>
</li>
<li<%= sidebar_current("docs-providers-profitbricks") %>>
<a href="/docs/providers/profitbricks/index.html">ProfitBricks</a>
</li>
<li<%= sidebar_current("docs-providers-rabbitmq") %>>
<a href="/docs/providers/rabbitmq/index.html">RabbitMQ</a>
</li>
<li<%= sidebar_current("docs-providers-rancher") %>>
<a href="/docs/providers/rancher/index.html">Rancher</a>
</li>
<li<%= sidebar_current("docs-providers-random") %>>
<a href="/docs/providers/random/index.html">Random</a>
</li>
<li<%= sidebar_current("docs-providers-rundeck") %>>
<a href="/docs/providers/rundeck/index.html">Rundeck</a>
</li>
<li<%= sidebar_current("docs-providers-scaleway") %>>
<a href="/docs/providers/scaleway/index.html">Scaleway</a>
</li>
<li<%= sidebar_current("docs-providers-softlayer") %>>
<a href="/docs/providers/softlayer/index.html">SoftLayer</a>
</li>
<li<%= sidebar_current("docs-providers-statuscake") %>>
<a href="/docs/providers/statuscake/index.html">StatusCake</a>
</li>
<li<%= sidebar_current("docs-providers-spotinst") %>>
<a href="/docs/providers/spotinst/index.html">Spotinst</a>
</li>
<li<%= sidebar_current("docs-providers-template") %>>
<a href="/docs/providers/template/index.html">Template</a>
</li>
<li<%= sidebar_current("docs-providers-terraform") %>>
<a href="/docs/providers/terraform/index.html">Terraform</a>
</li>
<li<%= sidebar_current("docs-providers-tls") %>>
<a href="/docs/providers/tls/index.html">TLS</a>
</li>
<li<%= sidebar_current("docs-providers-triton") %>>
<a href="/docs/providers/triton/index.html">Triton</a>
</li>
<li<%= sidebar_current("docs-providers-ultradns") %>>
<a href="/docs/providers/ultradns/index.html">UltraDNS</a>
</li>
<li<%= sidebar_current("docs-providers-vault") %>>
<a href="/docs/providers/vault/index.html">Vault</a>
</li>
<li<%= sidebar_current("docs-providers-vcd") %>>
<a href="/docs/providers/vcd/index.html">VMware vCloud Director</a>
</li>
<li<%= sidebar_current("docs-providers-vsphere") %>>
<a href="/docs/providers/vsphere/index.html">VMware vSphere</a>
</li>
</ul>
</li>
<li<%= sidebar_current(/^docs-provisioners/) %>>
<a href="/docs/provisioners/index.html">Provisioners</a>
<ul class="nav">
<li<%= sidebar_current("docs-provisioners-chef") %>>
<a href="/docs/provisioners/chef.html">chef</a>
</li>
<li<%= sidebar_current("docs-provisioners-connection") %>>
<a href="/docs/provisioners/connection.html">connection</a>
</li>
<li<%= sidebar_current("docs-provisioners-file") %>>
<a href="/docs/provisioners/file.html">file</a>
</li>
<li<%= sidebar_current("docs-provisioners-local") %>>
<a href="/docs/provisioners/local-exec.html">local-exec</a>
</li>
<li<%= sidebar_current("docs-provisioners-remote") %>>
<a href="/docs/provisioners/remote-exec.html">remote-exec</a>
</li>
<li<%= sidebar_current("docs-provisioners-null-resource") %>>
<a href="/docs/provisioners/null_resource.html">null_resource</a>
</li>
</ul>
</li>
<li<%= sidebar_current(/^docs-modules/) %>>
<a href="/docs/modules/index.html">Modules</a>
<ul class="nav">
<li<%= sidebar_current("docs-modules-usage") %>>
<a href="/docs/modules/usage.html">Usage</a>
</li>
<li<%= sidebar_current("docs-modules-sources") %>>
<a href="/docs/modules/sources.html">Sources</a>
</li>
<li<%= sidebar_current("docs-modules-create") %>>
<a href="/docs/modules/create.html">Creating Modules</a>
</li>
</ul>
</li>
<li<%= sidebar_current(/^docs-backends/) %>>
<a href="/docs/backends/index.html">Backends</a>
<ul class="nav">
<li<%= sidebar_current("docs-backends-init") %>>
<a href="/docs/backends/init.html">Init</a>
</li>
<li<%= sidebar_current("docs-backends-config") %>>
<a href="/docs/backends/config.html">Configuration</a>
</li>
<li<%= sidebar_current("docs-backends-state") %>>
<a href="/docs/backends/state.html">State Storage & Locking</a>
</li>
<li<%= sidebar_current("docs-backends-types") %>>
<a href="/docs/backends/types/index.html">Backend Types</a>
</li>
<!--
<li<%= sidebar_current("docs-backends-ops") %>>
<a href="/docs/backends/operations.html">Operations</a>
</li>
-->
</ul>
</li>
<li<%= sidebar_current(/^docs-plugins/) %>>
<a href="/docs/plugins/index.html">Plugins</a>
<ul class="nav">
<li<%= sidebar_current("docs-plugins-basics") %>>
<a href="/docs/plugins/basics.html">Basics</a>
</li>
<li<%= sidebar_current("docs-plugins-provider") %>>
<a href="/docs/plugins/provider.html">Provider</a>
</li>
<li<%= sidebar_current("docs-internals-plugins") %>>
<a href="/docs/internals/internal-plugins.html">Internals</a>
</li>
</ul>
</li>
<li<%= sidebar_current(/^docs-internals/) %>>
<a href="/docs/internals/index.html">Internals</a>
<ul class="nav">
<li<%= sidebar_current("docs-internals-debug") %>>
<a href="/docs/internals/debugging.html">Debugging Terraform</a>
</li>
<li<%= sidebar_current("docs-internals-graph") %>>
<a href="/docs/internals/graph.html">Resource Graph</a>
</li>
<li<%= sidebar_current("docs-internals-lifecycle") %>>
<a href="/docs/internals/lifecycle.html">Resource Lifecycle</a>
</li>
<li<%= sidebar_current("docs-internals-resource-addressing") %>>
<a href="/docs/internals/resource-addressing.html">Resource Addressing</a>
</li>
<li<%= sidebar_current("docs-internals-plugins") %>>
<a href="/docs/internals/internal-plugins.html">Internal Plugins</a>
</li>
</ul>
</li>
<li<%= sidebar_current(/^docs-enterprise/) %>>
<a href="/docs/enterprise/index.html">Terraform Enterprise</a>
<ul class="nav">
<li<%= sidebar_current("docs-enterprise-runs") %>>
<a href="/docs/enterprise/runs/index.html">Runs</a>
</li>
<li<%= sidebar_current("docs-enterprise-state") %>>
<a href="/docs/enterprise/state/index.html">State</a>
</li>
</ul>
</li>
</ul>
</div>
<% end %>
<%= yield %>
>>>>>>> 568c35750... Added all TFE state files
<% end %>

View File

@ -0,0 +1,22 @@
<% wrap_layout :inner do %>
<% content_for :sidebar do %>
<div class="docs-sidebar hidden-print affix-top" role="complementary">
<ul class="nav docs-sidenav">
<li>
<a href="/docs/enterprise/index.html">&laquo; Terraform Enterprise</a>
</li>
<li<%= sidebar_current(/^docs-enterprise-vcs-/) %>>
<a href="/docs/enterprise/vcs/index.html">VCS Integration</a>
<ul class="nav nav-visible">
<li<%= sidebar_current("docs-enterprise-vcs-git") %>>
<a href="/docs/enterprise/artifacts/git.html">Git</a>
</li>
</ul>
</li>
</ul>
</div>
<% end %>
<%= yield %>
<% end %>