Following the same behavior as gar_gce_auth for the sake of consistency and because it looks like it might have been the original intention as well, judging from the function's documentation.
Now the token is not only generated, but also automatically established internally in the library to be used for subsequent API calls.
Before this commit, one would have to write:
token <- gar_gce_auth_default()
gar_auth(token)
while now this is enough:
gar_gce_auth_default()
which maintains symmetry to how one would authorize using GCE credentials:
Following the same behavior as
gar_gce_auth
for the sake of consistency and because it looks like it might have been the original intention as well, judging from the function's documentation.Now the token is not only generated, but also automatically established internally in the library to be used for subsequent API calls.
Before this commit, one would have to write:
while now this is enough:
which maintains symmetry to how one would authorize using GCE credentials: