Closed jessereynolds closed 1 year ago
@jessereynolds I have re-tested this with the newest pecdm (https://github.com/puppetlabs/puppetlabs-pecdm/commit/4149814346d47a48282df81465713366e3482214) and it works for me, both apply and destroy. Can you please try this version?
@timidri looking good with commit 4149814346d47a48282df81465713366e3482214 on the fix-terraform-vars branch, thank you.
@jessereynolds Awesome! Closing the issue. /cc @ody
Describe the Bug
A re-iteration of the main issue that #99 sought to highlight.
pecdm only works correctly with AWS if you use us-west-2 when the region is specified via parameter to the
pecdm::provision
plan (and no environment variable such asAWS_REGION
is used).I've tried the following regions:
ap-southeast-2 us-east-1
Expected Behavior
Setting the region in the parameters to pecdm::provision should allow regions other than us-west-2 to be specified and the plan then able to complete successfully.
Steps to Reproduce
First reproduction case:
--var-file
Use the version of pecdm with the extra verbose output showing the output of pecdm::subplans::provision so the inventory resolution can be evaluated with stage set to true (skip the PE install, just build the infra):
ensure params.json contains (minus obvious redactions):
Results:
vpc_id
to:Environment
% bolt --version 3.26.1
% terraform --version Terraform v1.3.4 on darwin_amd64
Additional Context
Note that this is fixed by bumping the version of
puppetlabs-terraform
used to df32b49It is also fixed by calling the apply task twice, instead of apply and refresh, per #100 but @timidri's fix to
puppetlabs-terraform
is cleaner.Full output of
pecdm::provision
:Full output of
pecdm::destroy
: