So I found out I should not have been including quotes in my gce.ini file. Though, I'm still not able to authenticate, getting the following error:
libcloud.common.google.GoogleAuthError: 'Invalid authorization response, please check your credentials.' I've followed the instructions pretty closely, and have no idea how to begin troubleshooting this. On Thursday, April 23, 2015 at 4:48:59 PM UTC-4, Synaesthete wrote: > > I think this is more of a libcloud question, but I'm starting here hoping > others have encountered the same issue. > > I'm using the gce.py script found in the ansible repository to return a > dynamic inventory of my GCE instances. When I run > > ./gce.py --list > > > I get the following prompt: > > Please Go to the following URL and sign in: > > https://accounts.google.com/o/oauth2/auth?<some long URL> > > Enter Code: > > When I visit the URL I get a 404, so am not able to get a code. I thought > that by referencing the .pem file I derived for the service account, I > would not need further authentication. Additionally, I'd like to run this > script from a CI server... ideally all my authentication details would be > environment variables rather than stored in a file. And I can't exactly > manually authenticate on a CI server every time I access gce.py. > > Has anyone else run in to these issues? How are people CI-ing to GCE using > Ansible? > > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/bf118bf2-1c9b-4e6d-8242-fae6f7c8ab2a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
