Skip to content
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.

(CLOUD-184, CLOUD-205) Avoid ambiguity when using the AWS_REGION environment var #132

Conversation

garethr
Copy link
Contributor

@garethr garethr commented Mar 24, 2015

If using the AWS_REGION environment variable and a manifest where the
region property of one or more resources doesn't match you can see
unspecified behaviour. See
#117 for discussions.

This PR extracted from the above simply stops that from happening. If
the env is present and doesn't match All of the region properties then
we fail. This maintains the utility of the env var as an optimisation
but stops us shooting ourselves in the foot.

If using the AWS_REGION environment variable and a manifest where the
region property of one or more resources doesn't match you can see
unspecified behaviour. See
puppetlabs-toy-chest#117 for discussions.

This PR extracted from the above simply stops that from happening. If
the env is present and doesn't match All of the region properties then
we fail. This maintains the utility of the env var as an optimisation
but stops us shooting ourselves in the foot.
@garethr garethr modified the milestone: 1.0 Mar 24, 2015
@garethr garethr changed the title Avoid ambiguity when using the AWS_REGION environment var (CLOUD-184, CLOUD-205) Avoid ambiguity when using the AWS_REGION environment var Mar 25, 2015
@DavidS
Copy link
Contributor

DavidS commented Sep 1, 2015

You have missed the region property in lib/puppet/type/ec2_instance.rb.

ahenroid pushed a commit to ahenroid/puppetlabs-aws that referenced this pull request Jan 20, 2017
ahenroid pushed a commit to ahenroid/puppetlabs-aws that referenced this pull request Jan 20, 2017
@ahenroid
Copy link
Contributor

I updated and posted #401

@prozach prozach merged commit 919073e into puppetlabs-toy-chest:master Jan 24, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants