#build-harness (2020-01)
Help with the Cloud Posse build-harness https://github.com/cloudposse/build-harness
2020-01-07
@Erik Osterman (Cloud Posse) there’s another commit added to the terraform-docs PR which handles multiline description heredoc text.
@cytopia doesn’t the official terraform-docs
now support HCl2?
(i haven’t tested it yet)
v0.8.0-rc.1
does (also haven’t tested yet)
2020-01-14
I have successfully tried v0.8-rc.2
. Works pretty well. Seems to handle every case out-of-the-box that came up as GitHub issues with the awk
version.
Awesome!
I need to update our package for that
2020-01-17
Hi all. I’m having an issue when running make readme
for a PR on cloudposse/terraform-aws-vpc-flow-logs-s3-bucket
make readme
curl --retry 3 --retry-delay 5 --fail -sSL -o /Users/andrewmackett/git/terraform-aws-vpc-flow-logs-s3-bucket/build-harness/vendor/terraform-docs <https://github.com/segmentio/terraform-docs/releases/download/v0.4.5/terraform-docs-v0.4.5-darwin-amd64> && chmod +x /Users/andrewmackett/git/terraform-aws-vpc-flow-logs-s3-bucket/build-harness/vendor/terraform-docs
make: gomplate: No such file or directory
make: *** [readme/build] Error 1
Any suggestions?
More detail here: https://github.com/cloudposse/terraform-aws-vpc-flow-logs-s3-bucket/pull/4#issuecomment-575714601
When using this module with the default variable values I receive the error: Error: MalformedPolicyDocumentException: The new key policy will not allow you to update the key policy in the future. …
can you try make readme/init
(also, we’re working on a GitHub action to eliminate this!)
@Andriy Knysh (Cloud Posse) is…
2020-01-18
The problem was gomplate
not being found. I thought that was being installed in the make readme/deps
step but perhaps I have an issue with my $GOPATH
or something like that.
Anyway, using brew install gomplate
fixed the situation and make readme
worked fine after that. Thanks for the help!
@Andrew Mackett seems like we have some bug in build-harness
- others too have had problems with it not installing gomplate or not being installed in the right place
your workaround is good for now!