Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for TF_KEY_NAME #33

Open
GeertJohan opened this issue Mar 24, 2016 · 2 comments
Open

Support for TF_KEY_NAME #33

GeertJohan opened this issue Mar 24, 2016 · 2 comments

Comments

@GeertJohan
Copy link
Contributor

Hi,

I the TF_KEY_NAME override in the source, which is very useful because some servers are only accessable on their private_ip.
Should TF_KEY_NAME be documented? And will it stay supported?
Thanks

@adammck
Copy link
Owner

adammck commented Mar 25, 2016

Yes, on both counts. It was added by #28, for the same use-case, but not documented at the time. It will continue to be supported indefinitely, although I'd like to add a --private argument to achieve the same thing.

@simt2
Copy link

simt2 commented Jan 18, 2018

It took me some time and debugging to find this hidden feature :)

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

No branches or pull requests

3 participants