Use the built-in alert helpers

This commit is contained in:
Seth Vargo 2014-10-22 10:01:17 -04:00
parent 073a0f76c5
commit 9ac9ab6706
9 changed files with 19 additions and 50 deletions

View File

@ -15,13 +15,11 @@ generate plans, refresh state, and more. This page documents
the details of what are contained in this graph, what types
of nodes there are, and how the edges of the graph are determined.
<div class="alert alert-block alert-warning">
<strong>Advanced Topic!</strong> This page covers technical details
~> **Advanced Topic!** This page covers technical details
of Terraform. You don't need to understand these details to
effectively use Terraform. The details are documented here for
those who wish to learn about them without having to go
spelunking through the source code.
</div>
## Graph Nodes

View File

@ -14,8 +14,6 @@ of this section is to remove any notion of "magic" from Terraform.
We want you to be able to trust and understand what Terraform is
doing to function.
<div class="alert alert-block alert-info">
<strong>Note:</strong> Knowledge of Terraform internals is not
-> **Note:** Knowledge of Terraform internals is not
required to use Terraform. If you aren't interested in the internals
of Terraform, you may safely skip this section.
</div>

View File

@ -13,13 +13,11 @@ state machines. Understanding this lifecycle can help better understand
how Terraform generates an execution plan, how it safely executes that
plan, and what the resource provider is doing throughout all of this.
<div class="alert alert-block alert-warning">
<strong>Advanced Topic!</strong> This page covers technical details
~> **Advanced Topic!** This page covers technical details
of Terraform. You don't need to understand these details to
effectively use Terraform. The details are documented here for
those who wish to learn about them without having to go
spelunking through the source code.
</div>
## Lifecycle

View File

@ -12,12 +12,10 @@ This page documents the basics of how the plugin system in Terraform
works, and how to setup a basic development environment for plugin development
if you're writing a Terraform plugin.
<div class="alert alert-block alert-warning">
<strong>Advanced topic!</strong> Plugin development is a highly advanced
~> **Advanced topic!** Plugin development is a highly advanced
topic in Terraform, and is not required knowledge for day-to-day usage.
If you don't plan on writing any plugins, we recommend not reading
this section of the documentation.
</div>
## How it Works
@ -70,12 +68,10 @@ Developing a plugin is simple. The only knowledge necessary to write
a plugin is basic command-line skills and basic knowledge of the
[Go programming language](http://golang.org).
<div class="alert alert-block alert-info">
<strong>Note:</strong> A common pitfall is not properly setting up a
-> **Note:** A common pitfall is not properly setting up a
<code>$GOPATH</code>. This can lead to strange errors. You can read more about
this <a href="https://golang.org/doc/code.html">here</a> to familiarize
this [here](https://golang.org/doc/code.html) to familiarize
yourself.
</div>
Create a new Go project somewhere in your `$GOPATH`. If you're a
GitHub user, we recommend creating the project in the directory

View File

@ -18,9 +18,7 @@ to write plugins for Terraform. It does not hold your hand through the
process, however, and expects a relatively high level of understanding
of Go, provider semantics, Unix, etc.
<div class="alert alert-block alert-warning">
<strong>Advanced topic!</strong> Plugin development is a highly advanced
~> **Advanced topic!** Plugin development is a highly advanced
topic in Terraform, and is not required knowledge for day-to-day usage.
If you don't plan on writing any plugins, we recommend not reading
this section of the documentation.
</div>

View File

@ -22,12 +22,10 @@ The primary reasons to care about provider plugins are:
* You want to write a completely new provider for custom, internal
systems such as a private inventory management system.
<div class="alert alert-block alert-warning">
<strong>Advanced topic!</strong> Plugin development is a highly advanced
~> **Advanced topic!** Plugin development is a highly advanced
topic in Terraform, and is not required knowledge for day-to-day usage.
If you don't plan on writing any plugins, we recommend not reading
this section of the documentation.
</div>
If you're interested in provider development, then read on. The remainder
of this page will assume you're familiar with

View File

@ -16,14 +16,10 @@ ask for input of things such as variables and API keys. If you want to
conitnue using the example, you should save those parameters in a
"terraform.tfvars" file or in a `provider` config bock.
<div class="alert alert-block alert-warning">
<div>
<strong>Note:</strong> The examples use real providers that launch
<em>real</em> resources. That means they can cost money to
experiment with. To avoid unexpected charges, be sure to understand the price
of resources before launching them, and verify any unneeded resources
are cleaned up afterwards.</div>
</div>
~> **Warning!** The examples use real providers that launch _real_ resources.
That means they can cost money to experiment with. To avoid unexpected charges,
be sure to understand the price of resources before launching them, and verify
any unneeded resources are cleaned up afterwards.
Experimenting in this way can help you learn how the Terraform lifecycle
works, as well as how to repeatedly create and destroy infrastructure.

View File

@ -29,16 +29,10 @@ If you already have an AWS account, you may be charged some
amount of money, but it shouldn't be more than a few dollars
at most.
<div class="alert alert-block alert-warning">
<p>
<strong>Note:</strong> If you're not using an account that qualifies
under the AWS
<a href="http://aws.amazon.com/free/">free-tier</a>,
you may be charged to run these examples. The most you should
be charged should only be a few dollars, but we're not responsible
for any charges that may incur.
</p>
</div>
~> **Warning!** If you're not using an account that qualifies under the AWS
[free-tier](http://aws.amazon.com/free/), you may be charged to run these
examples. The most you should be charged should only be a few dollars, but
we're not responsible for any charges that may incur.
## Configuration

View File

@ -21,16 +21,9 @@ This section of the getting started will cover the basics of using modules.
Writing modules is covered in more detail in the
[modules documentation](/docs/modules/index.html).
<div class="alert alert-block alert-warning">
<p>
<strong>Warning:</strong> The examples on this page are
<em>not eligible</em> for the
AWS
<a href="http://aws.amazon.com/free/">free-tier</a>. Do not execute
the examples on this page unless you're willing to spend a small
amount of money.
</p>
</div>
~> **Warning!** The examples on this page are _**not** eligible_ for the AWS
[free-tier](http://aws.amazon.com/free/). Do not execute the examples on this
page unless you're willing to spend a small amount of money.
## Using Modules