[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Cloud test scripts



If you use a service account instead of the default credentials you won't need gcloud in the loop. You do need to store the key somewhere (its a json file) and use that for the API auth.

https://cloud.google.com/iam/docs/understanding-service-accounts

-----
Zach Marano
zmarano@google.com


On Sun, Aug 19, 2018 at 2:50 PM Tomasz Rybak <tomasz.rybak@post.pl> wrote:
Hello.
If some of you noticed, I started playing with our testing scripts.

I pushed small change to main branch; basically I had to explicitly
use credentials managed by gcloud tools to be able to run our tests.
If somebody knows more about how GCE manages credentials, please
correct me: I could not get our scripts running without those
changes, but maybe there is other way.

Another change is in new branch: key_management. I want to return
to ability to use personal SSH keys. For automated tests having
auto-generated SSH keys is very good idea, but for some experiments,
debugging, etc., I want to be able to use my key, and to login into
machine on my own. Besides - I'm using obsolete parameters --key-file
and --key-name now ;-)
On more serious note - I'm not yet sure how to manage it; that's why
there is new branch. It'll probably be some time before I have
some idea which is useful in all use cases and not to comples.

To finish with more positive note - I was able to run those scripts
from my main machine, and they run (yay!) - although there were
some test failures. But at least they are still usable with
unstable +Google repository (no need for pip, or other non-packaged
software).

Best regards.

--
Tomasz Rybak, Debian Developer <serpent@debian.org>
GPG: A565 CE64 F866 A258 4DDC F9C7 ECB7 3E37 E887 AA8C

Reply to: