[Documentation Issue]

[Avemark]

"Setup Authentication" link does not actually link to Authentication information. Further links on the following page leads to an "authentication guide" that does not as much explain authentication as inform you that you should be running the code on a machine where authentication is already available.

A mention on where to get credentials, and an example or description of a credential json would be very helpful here. Also, I'd suggest a direct link to the authentication guide from the first page.

[quartzmo]

@Avemark Thank you for reporting the broken link at "Setup Authentication". And I agree that the top-level authentication guide for google-cloud-ruby that you link seems incomplete.

What do you think of the authentication guide for google-cloud-datastore? Is it adequate?

[quartzmo]

A mention on where to get credentials, and an example or description of a credential json would be very helpful here.

@Avemark If we fix the "Setup Authentication" to link to an authentication guide that is similar to the authentication guide for google-cloud-datastore (but adapted to google-cloud-dialogflow), will that work for you?

[quartzmo]

Should the scope of this issue be expanded to all generated packages that currently lack an authentication guide?

[Avemark]

@quartzmo The linked authentication guide seems a lot more thorough, and a direct link to something similar would have cut down on the time needed for my discovery process a lot.

[quartzmo]

@blowmage @dazuma @TheRoyalTnetennba Is there any reason why the generated packages do not have an AUTHENTICATION.md file? (See datastore/AUTHENTICATION.md for example.)

If not, do we want one? If so, should I add them manually, or can I update the generation somehow?

[blowmage]

It is not part of the generation process. We would have to add them manually, or configure each gem's synth.py script to generate one.

[quartzmo]

I'll start work on a PR to add this to synth.py.