Gary Larizza

The issue with that is that the plan file is binary encoded and not legible. Only the output from `terraform plan` is in plaintext, so that would need to be...

Followed by something like this to echo out `plan` output: https://github.com/glarizza/jenkins-devops-libs/commit/58e2d165c3b4691e8548d13b8e3abaf492c7a3a8 If you think this method works I can open a PR to start the conversation there?

Ahh, you're correct - I reacted to reading the Plan file directly and not to the `terraform show` command (which I would expect to work). That's certainly an option without...

One big difference with using `terraform show` is that the output doesn't match the output of the initial plan (it doesn't get you the nicely formatted diff). There is a...

Is there currently any way to access the contents of the `plan_output` variable from the location where we're calling `terraform.plan {}`? I need to access that variable so I can...

An example of what I'm doing (with an AWFUL lot of noise) can be viewed here: https://github.com/openinfrastructure/jenkins-terraform-pipelines/pull/1

Yep, that's what I was looking for! I've since finished the engagement where I was going to use this code, and they decided to implement it via shell code first...

I just recently started to get a similar stacktrace within the past week: ``` ERRO[0017] Listing AWS::AppRunner::Service failed: TypeNotFoundException: The type 'AWS::AppRunner::Service' cannot be found. us-west-1 - MemoryDBUser - default...

I'm wary of this because the last time I tested it out, it actually did NOT work for me (see: https://github.com/glarizza/puppet-property_list_key/issues/12#issuecomment-31022799 ). I will need to test on a case-sensitive...

@cdenneen I've got the "OR" lines in there to accommodate users of each (either bundler or system gems). Bundler is probably overkill if you're just managing workstations via Puppet and...