817be7b23f
website: update backend/swift examples to use versioning
...
Since object versioning is a best practice the docs should have all the
examples containing it by default.
2018-11-06 18:18:46 -06:00
58cb47d108
website: backend/swift fix bad link for object versioning
...
The displayed link said `expire_after` but really is a link to
`archive_container` so update the link to read the right data.
fixes #19005
2018-11-06 18:18:46 -06:00
ddc30b6546
website: backend/swift add docs link for expire_after
...
Provide a link to the OpenStack Swift docs for the object expiration
feature that is used by the `expire_after` field.
2018-11-06 18:18:45 -06:00
b31aab4469
website: fix backend/swift links to Swift docs
...
The links to the OpenStack Swift documentation were broken due to
changes on the OpenStack website.
2018-11-06 18:18:45 -06:00
027b107268
website: update deprecated backend/swift docs
...
Update the examples and docs to not directly reference deprecated
fields.
2018-11-06 18:18:45 -06:00
52a1b22f7a
Implement the remote enhanced backend
...
This is a refactored version of the `remote` backend that was initially added to Terraform v0.11.8 which should now be compatible with v0.12.0.
2018-11-06 16:29:46 +01:00
5fa624c55e
website: update terraform_remote_state syntax in backend docs
2018-10-29 09:22:21 -07:00
642cdd331f
Fix typo.
2018-10-22 14:26:33 -07:00
775f8a9626
Make sure we always set a custom header
...
This is for TFE to recognize were the calls come from.
2018-10-15 20:33:42 +02:00
77b9fad7f0
backend/manta: deprecate camelcase attribute name
...
This change is needed (next to making it consistent as its the only attribute name that uses camelcase) because passing that attribute objectName in the update `terraform_remote_state` resource, ended up giving me this error: https://github.com/hashicorp/terraform/blob/master/helper/schema/schema.go#L736
2018-08-29 20:22:04 +02:00
cf8516287e
website: Classify remote backends as a preview release
2018-08-24 17:10:46 -05:00
6e5259911e
PTFE not ready for use with this remote version
2018-08-24 13:10:28 -07:00
4612a71414
website: revise docs for remote backend and credentials config
2018-08-22 14:30:23 -07:00
d0fec98833
Merge pull request #18647 from hashicorp/paultyng-patch-1
...
Clarifying the language around "root outputs"
2018-08-17 09:27:05 -04:00
7049d973a9
Do not use the TFE_TOKEN env variable
...
Instead promote the use of shared credentials using the CLI Config File
2018-08-10 20:20:16 +02:00
22bdc44cb1
Clarifying the language around "root outputs"
2018-08-09 13:20:45 -04:00
7fb2d1b8de
Implement the Enterprise enhanced remote backend
2018-08-03 22:22:55 +02:00
2487af1945
website: atlas backend requires https protocol in address ( #18585 )
...
Just providing the hostname won't work. This commit adds an example and fixes
the explanation.
2018-08-01 17:33:11 -07:00
a51fc61014
website: Revise "atlas" backend page
...
Add links to important docs (like user tokens), and explain that this isn't part
of our recommended primary workflows anymore.
2018-07-09 15:28:30 -07:00
e2373c8073
website: Using demo.consul.io requires scheme = "https"
...
Following the examples as they were previously would cause errors
accessing demo.consul.io. Now we consistently set the scheme to https for
all examples that use demo.consul.io.
This also includes some other updates to the URLs, since the Consul demo
has been rebuilt with a different based configuration, and some general
formatting and copyediting changes in the Consul example.
2018-06-22 10:18:27 -07:00
e552897c52
Fix typo (wit -> with) for etcdv3 backend docs
2018-06-11 11:46:17 -07:00
b6fbb42be6
Add required DynamoDB IAM permissions for state locking to S3 backend docs
2018-04-04 10:38:52 +01:00
6c2b2515bd
Update reference to deprecated argument in S3 backend docs
2018-04-04 09:20:08 +01:00
5458ea9aff
update etcd documentation links
...
Add missing link to ectdv3.
Update etcd v2 link to the current v2 README, which highlights the pending
deprecation.
2018-02-15 17:13:24 -05:00
856b852ac2
Correct typo
2018-01-24 11:02:12 -05:00
e4cdbd6c9f
Merge pull request #16936 from negz/gcskeys
...
Support 'customer supplied encryption keys' in the GCS backend
2018-01-09 01:17:35 -08:00
d1a678db0d
Merge pull request #16915 from hashicorp/jbardin/gcs-docs
...
add gcs to the backends that support workspaces in the documentation
2018-01-08 16:47:45 -05:00
191cf283d5
backend/manta: Support Triton RBAC
...
Triton Manta allows an account other than the main triton account to be used via RBAC.
Here we expose the SDC_USER / TRITON_USER options to the backend so that a user can be specified.
2018-01-03 12:12:46 -08:00
011841124b
Support 'customer supplied encryption keys' in the GCS backend
...
https://cloud.google.com/storage/docs/encryption#customer-supplied
GCS state created using customer supplied encryption keys can only be read or
modified using the same key.
2017-12-17 19:27:52 -08:00
ccb90d5b6b
add gcs to the backends that support workspaces
...
Also add the term "workspaces" to the `prefix` documentation.
2017-12-14 10:25:03 -05:00
c729bdff43
website: guide for using the S3 backend with multiple AWS accounts
...
Users commonly ask how the S3 backend can be used in an organization that
splits its infrastructure across many AWS accounts.
We've traditionally shied away from making specific recommendations here
because we can't possibly anticipate the different standards and
regulations that constrain each user. This new section attempts to
describe one possible approach that works well with Terraform's workflow,
with the goal that users make adjustments to it taking into account their
unique needs.
Since we are intentionally not being prescriptive here -- instead
considering this just one of many approaches -- it deviates from our usual
active writing style in several places to avoid giving the impression that
these are instructions to be followed exactly, which in some cases
requires the use of passive voice even though that is contrary to our
documentation style guide. For similar reasons, this section is also
light on specific code examples, since we do not wish to encourage users
to just copy-paste the examples without thinking through the consequences.
2017-12-08 16:53:43 -08:00
3538f832b0
website: update "atlas" backend to recommend using ATLAS_TOKEN environment variable
2017-12-05 11:34:05 -08:00
d6b8e27086
website: Document required S3 IAM actions for S3 backend
2017-12-05 11:31:31 -08:00
aaedf255c3
backend/s3: allow skipping the region check ( #16757 )
...
Without the possibility to skip this check, it’s not possible to use a custom region with a third-party service that mimicks the S3 API.
2017-12-05 11:19:36 -08:00
323654a716
Fixed documentation of azurerm backend advanced access variables ( #16552 )
...
Signed-off-by: Dominik Lekse <dominik@lekse.de>
2017-11-06 16:54:30 +00:00
1fd0f803e4
Migrate Manta Remote state to be a backend
...
This PR changes manta from being a legacy remote state client to a new backend type. This also includes creating a simple lock within manta
This PR also unifies the way the triton client is configured (the schema) and also uses the same env vars to set the backend up
It is important to note that if the remote state path does not exist, then the backend will create that path. This means the user doesn't need to fall into a chicken and egg situation of creating the directory in advance before interacting with it
2017-10-30 18:36:50 +02:00
b5d3559d2d
website: refine the description of the azurerm backend
2017-10-27 17:26:37 -07:00
927085289d
backend/remote-state/gcs: Implement the "region" config option.
...
This allows to select the region in which a bucket is created.
This copies behavior from the Google Cloud provider.
2017-10-27 16:52:21 -04:00
9583d0945c
backend/remote-state/gcs: Add support for the GOOGLE_PROJECT environment variable.
...
This copies behavior from the Google Cloud provider.
2017-10-27 16:52:21 -04:00
52e6159219
backend/remote-state/gcs: Improve "bucket" and "credentials" documentation.
2017-10-27 16:52:21 -04:00
df386d3133
backend/remote-state/gcs: Automatically create the bucket if needed.
...
This resurrects the previously documented but unused "project" option.
This option is required to create buckets (so they are associated with the
right cloud project) but not to access the buckets later on (because their
names are globally unique).
2017-10-27 16:52:21 -04:00
5205c63bc9
website/docs/backends/types/gcs.html.md: Update.
...
* Remove the (unused) "project" option.
* Mark the "credentials" option as optional; document behavior when
unset.
* Mark the "path" option as deprecated (was: legacy) to match
Terraform's terminology.
2017-10-27 16:52:21 -04:00
14bfbf0617
backend/remote-state/gcs: Document the "prefix" option.
...
"state_dir" has been renamed to "prefix" to better fix the GCS
terminology.
2017-10-27 16:51:21 -04:00
91442b7146
Merge pull request #15680 from brunomcustodio/etcdv3-backend
...
[WIP] etcd v3 backend with lock support.
2017-10-03 14:15:58 -04:00
d477d1f6d4
Merge pull request #15553 from bonifaido/custom_s3_backend
...
Allow non-AWS S3 backends
2017-10-02 19:39:48 -04:00
524c3934c6
Add TLS support.
2017-09-09 08:03:59 +01:00
6daf1d9d84
Allow for username and password to be read from envvars.
2017-09-08 23:41:27 +01:00
8f7b315037
Add documentation.
2017-09-08 23:40:05 +01:00
cbb512d374
Updating the AzureRM Backend Documentation ( #15990 )
...
* Updating to reference this has been renamed
* Clarifying Blob Storage
2017-09-04 07:56:16 +01:00
21b287e919
backend/consul: allow specifying various Consul client security options
...
These new options are equivalent to the consul CLI arguments -ca-file, -client-cert and -client-key.
2017-08-23 09:47:21 -07:00
2e0c1d07ae
Merge #15793 : Locking support in HTTP remote backend
2017-08-22 09:43:38 -07:00
e5029de439
Update remote/http doc to match locking changes
2017-08-20 05:59:34 -07:00
216a68a41b
update backend docs to reflect new azurerm name
...
The backend has been renamed. Using the old name in the config will
trigger a deprecation warning, but the implementation and the
documentation is the same.
2017-08-17 12:55:48 -04:00
f9e8e54835
backend: convert Azure remote state to a backend
...
Added locking support via blob leasing (requires that an empty state is
created before any lock can be acquired.
Added support for "environments" in much the same way as the S3 backend.
2017-08-17 16:32:17 +01:00
81f9c78122
Adding `resource_group_name` back in, fixes #15610 ( #15809 )
2017-08-15 11:54:48 +01:00
06b4b509d7
Doc state/http supports_locking
2017-08-13 09:49:49 -07:00
f63b216016
Update S3 backend docs to reflect new workspaces
...
Explain the path generated for state files when using workspaces.
2017-07-28 15:08:24 -04:00
f6c77339f2
Allow non-AWS S3 backends
...
This commit makes sts, metadata and other AWS related API calls optional, thus the backend initialization will not send non-AWS API tokens to AWS APIs
2017-07-14 13:08:47 +02:00
5066fa2151
Merge pull request #13871 from fatmcgav/swift_move_to_backend
...
Move Swift remote state to backend
2017-06-27 16:23:46 -04:00
4b85e91ac5
Update s3.html.md ( #15299 )
2017-06-27 18:57:38 +03:00
22f36a6e43
Document new field for S3 backend
2017-06-22 21:01:44 +01:00
af5467b9fd
website: Update swift backend documentation
2017-06-13 22:04:02 +01:00
7ed70bb00e
website: new filesystem layout for core/provider split
...
This repo now contains only the core docs, with other content moving elsewhere.
2017-06-13 11:25:32 -07:00
Doug Goldstein