Skip to content
This repository has been archived by the owner on Jan 25, 2023. It is now read-only.

Allow specification of non-default VPC #25

Closed
boldandbusted opened this issue Nov 22, 2017 · 4 comments
Closed

Allow specification of non-default VPC #25

boldandbusted opened this issue Nov 22, 2017 · 4 comments

Comments

@boldandbusted
Copy link

The Consul TF Registry module allows this. I think I see what changes were made there, and I hope I can make a PR that holds equivalent changes for this module (and how it uses the Consul module itself). I know that the code in the root of this repo is for "examples" and "testing", but I want to be fully lazy and have it also work for a real production setup as well as for testing purposes. ;)

@brikis98
Copy link
Collaborator

It might be better to create another folder under examples that contains a more production-ready module.

@boldandbusted
Copy link
Author

See #26. :)

@jasonmcintosh
Copy link
Contributor

#39 should now have this fixed?

@brikis98
Copy link
Collaborator

Yes, both examples now allow you to use a non-default VPC.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants