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: CHANGELOG.md
+5-6Lines changed: 5 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,16 @@
1
1
## 0.4.2 (Unreleased)
2
+
*[PR-9](https://github.com/opencredo/terrahelp/pull/9) Cater for terraform 0.7.x list and map variables (resolves [#8](https://github.com/opencredo/terrahelp/issues/8))
3
+
* Updated examples and command line docs
4
+
* Builds against Go 1.7.3
5
+
* Confirmed testing against Vault 0.5.2
2
6
3
7
## 0.4.1
4
8
* Add new `vault-cli` provider to use the `vault` command line tool rather than talking to the vault API.
5
9
6
10
## 0.4.0
7
11
**Note: This release contains breaking changes!!**
8
12
9
-
Terrahelp will now ignore stdin input if a `-file` flag is present.
10
-
11
-
**The `-file` flag will no longer default to terraform.tfstate and terraform.tfstate.backup.**
This is part of resolving [#5](https://github.com/opencredo/terrahelp/issues/5)
13
+
*[PR-6](https://github.com/opencredo/terrahelp/pull/6) Terrahelp will now ignore stdin input if a `-file` flag is present. The `-file` flag will no longer default to terraform.tfstate and terraform.tfstate.backup (part of resolving [#5](https://github.com/opencredo/terrahelp/issues/5))
Terrahelp uses [govendor](https://github.com/kardianos/govendor) to manage it's dependencies, and currently also checks them into Git to enable a seamless build experience. However should you wish to change / upgrade any of these, you can get govendor, and then run the appropriate commands (e.g sync, fetch etc)
83
+
84
+
go get -u github.com/kardianos/govendor
85
+
govendor sync
86
+
87
+
*Build it*
81
88
82
89
go install
83
90
84
-
Test it
91
+
*Test it*
85
92
86
93
go test -v ./...
87
94
88
-
Run it:
95
+
*Run it:*
89
96
90
97
terrahelp -v
91
98
92
-
Want to cross compile it:
99
+
*Want to cross compile it?*
93
100
94
101
env GOOS=darwin GOARCH=amd64 go build -o=terrahelp-darwin-amd64
95
102
env GOOS=linux GOARCH=amd64 go build -o=terrahelp-linux-amd64
This example contains a very simple terraform setup composed entirely of
4
-
local resources (e.g. template resource) and exists in order to demonstrate how
5
-
you can do masking of sensitive data which may be output from varius terraform
6
-
commands.
3
+
This example contains a very simple terraform setup composed entirely of local resources (e.g. template resource) and exists in order to demonstrate how you can do masking of sensitive data which may be output from varius terraform commands.
7
4
8
-
This example is completely safe to run and will not land up costing you any
9
-
money in a cloud provider!
5
+
This example is completely safe to run and will not land up costing you any money in a cloud provider! It currently demonstrates a terraform 0.7.7 based setup which includes the new lists and maps functionality.
10
6
11
-
The CLI itself offers a more comprehensive view of the various options available,
12
-
so please use this if you need more info.
7
+
The CLI itself offers a more comprehensive view of the various options available, so please use this if you need more info.
13
8
14
9
### Simple inline masking of terraform output
15
10
16
-
This example will demonstrate how you can use the `mask` command in order to mask
17
-
sensitive data which may be exposed when performing terraform actions.
11
+
This example will demonstrate how you can use the `mask` command in order to mask sensitive data which may be exposed when performing terraform actions.
18
12
19
13
* Run a `terraform plan` as normal
20
14
21
15
terraform plan
22
16
23
17
* Inspect the result which should look something like below:
24
18
25
-
Refreshing Terraform state prior to plan...
19
+
Refreshing Terraform state in-memory prior to plan...
20
+
The refreshed state will be used to calculate this plan, but
21
+
will not be persisted to local or remote state storage.
26
22
27
-
The Terraform execution plan has been generated and is shown below.
28
-
Resources are shown in alphabetical order for quick scanning. Green resources
29
-
will be created (or destroyed and then created if an existing resource
30
-
exists), yellow resources are being changed in-place, and red resources
31
-
will be destroyed.
23
+
...
32
24
33
-
Note: You didn't specify an "-out" parameter to save this plan, so when
34
-
"apply" is called, Terraform can't guarantee this is what will execute.
To change the mask character and/or length, you can use the `-maskchar` and `-numchars`
77
-
flags, e.g. `terraform plan | terrahelp mask -maskchar=# -numchars=3`
69
+
To change the mask character and/or length, you can use the `-maskchar` and `-numchars` flags, e.g. `terraform plan | terrahelp mask -maskchar=# -numchars=3`
78
70
79
-
By default, the mask command will also attempt to detect whether any previous sensitive data
80
-
may be exposed, and if so will mask this as well. This may happen for example when changing the
81
-
value of one sensitive value to another e.g.
71
+
By default, the mask command will also attempt to detect whether any previous sensitive data may be exposed, and if so will mask this as well. This may happen for example when changing the value of one sensitive value to another e.g.
82
72
83
73
+ template_file.example
84
74
rendered: "" => "<computed>"
@@ -101,6 +91,5 @@ In which case the resulting mask will look as follows
101
91
If you want to suppress this default behaviour you can use the `-prev=false`
102
92
103
93
### How does it work out what is considered sensitive?
104
-
At present, `terrahelp` relies on using the `terraform.tfvars` file as the mechanism to
105
-
indicate which values should be considered sensitive, and thus masked out when detected.
94
+
At present, `terrahelp` relies on using the `terraform.tfvars` file as the mechanism to indicate which values should be considered sensitive, and thus masked out when detected.
0 commit comments