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

Allow connection by IP also #45

Open
ghost opened this issue May 21, 2016 · 5 comments
Open

Allow connection by IP also #45

ghost opened this issue May 21, 2016 · 5 comments
Assignees

Comments

@ghost
Copy link

ghost commented May 21, 2016

I have noticed that by default I have to connect by DNS name (using digitalocean_droplet); it would be nice to be able to pass a switch (maybe --ipv4) and connect directly by IP instead of using DNS.

This is a problem because if you directly provision with TF and then try to run ansible using terraform.py as the "dynamic inventory" you're not able to connect because the DNS records do not exist.

@sean-abbott
Copy link
Collaborator

+1

@sean-abbott
Copy link
Collaborator

Along with #47, where I suggested config options, I would like to default to private IP without needing any tags.

@sean-abbott
Copy link
Collaborator

I modified the name assignment of aws_host to achieve this in a hacked fashion:

name = resource['primary']['attributes']['private_ip']

But a more permanent solution would be nice.

@stevendborrelli
Copy link

stevendborrelli commented Jul 8, 2016

I agree with this. It would be nice to have the option of using private IPs.

We probably also need to rethink options so that ENV vars can be used, since ansible will not send arguments down to the inventory script.

@sean-abbott
Copy link
Collaborator

ENV vars are ok, but would prefer config options from a code-sharing standpoint. I find things that require you source env vars before running to be more fraught with peril than stuff that allows you give a one liner to your coworkers.

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

4 participants