Skip to content
This repository was archived by the owner on Feb 11, 2022. It is now read-only.

Conversation

@mkubenka
Copy link

It should be possible to override region from Vagrantfile when using AWS profile files.

Probably fix #473

@mitodrummer
Copy link

Can this be merged? I also cannot switch from us-east-1 in my vagrant config.

@albertsj1
Copy link

Having this problem as well when using aws_profile instead of access and secret key. Please merge.

@hvpareja
Copy link

Seems like this went out of the radar?

@mkubenka
Copy link
Author

mkubenka commented Jun 17, 2017

I have created custom Gem with this change:

vagrant plugin uninstall vagrant-aws
vagrant plugin install vagrant-aws-mkubenka --plugin-version "0.7.2.pre.10"

@matttrach
Copy link

Another work around is to remove the "region" variable from your .aws/config, but this could affect how your aws cli works...

@naviat
Copy link

naviat commented Nov 19, 2018

I have created custom Gem with this change:

vagrant plugin uninstall vagrant-aws
vagrant plugin install vagrant-aws-mkubenka --plugin-version "0.7.2.pre.10"

Any update without this change? @mkubenka Could you guide how to use your plugin in Vagrantfile? sorry, I'm new to vagrant

elconde pushed a commit to elconde/vagrant-aws that referenced this pull request Dec 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aws.region is not loaded from Vagrantfile

6 participants