You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,14 +1,14 @@
1
1
# terraform-backend-hsdp
2
2
An extendable HTTP backend implementation for terraform
3
3
4
-
# Features
4
+
##Features
5
5
6
6
* Encrypt state at rest with AES-256-GCM
7
7
* Extensible store: currently supports S3, more to come
8
8
* HSDP UAA integration: use LDAP / functional account credentials for auth
9
9
* Allow list support: restrict use of an instance backend to specific accounts
10
10
11
-
# Overview
11
+
##Overview
12
12
13
13
The primary goal of this project is to offer storage of [Terraform state](https://www.terraform.io/docs/state/index.html) on the HSDP platform with little to no setup required.
14
14
Currently, we use CF credentials to authenticate access to the backend.
@@ -18,18 +18,18 @@ Future iterations may introduce service key credentials similar to the HSDP Dock
18
18
19
19
The core is derived from [bhoriuchi/terraform-backend-http](https://github.com/bhoriuchi/terraform-backend-http)
20
20
21
-
# Install
21
+
##Install
22
22
When self-hosting, you should deploy both the S3 bucket and the application deployment
23
23
in a separate space in order to limit who has access. Terraform state will contain operator
24
24
level secrets so only operators within your organization should have access.
25
25
26
-
## Provision an S3 bucket
26
+
###Provision an S3 bucket
27
27
Create an S3 bucket:
28
28
```shell
29
29
cf cs hsdp-s3 s3_bucket my-tfstate-bucket
30
30
```
31
31
32
-
## Deploy the service
32
+
###Deploy the service
33
33
34
34
Use the following `manifest.yml` as an example
35
35
@@ -62,13 +62,14 @@ cf push -f manifest.yml
62
62
After a few seconds you should have a running backend
0 commit comments