Page MenuHomePhabricator

Updated the docs so chatbots can use the Conduit API
ClosedPublic

Authored by jcox on Aug 24 2016, 8:25 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 26, 9:41 PM
Unknown Object (File)
Feb 7 2024, 6:11 PM
Unknown Object (File)
Feb 6 2024, 11:15 AM
Unknown Object (File)
Jan 31 2024, 9:59 AM
Unknown Object (File)
Jan 30 2024, 6:37 AM
Unknown Object (File)
Jan 22 2024, 12:06 PM
Unknown Object (File)
Jan 12 2024, 10:35 AM
Unknown Object (File)
Jan 10 2024, 3:32 AM
Subscribers

Details

Summary

Previously, the chatbot docs instructed users to get certificates for the conduit API and put the cert in a conduit.cert config key. In order to get the chatbot to work, I needed to instead get an API key and put it in the conduit.token config entry.

Test Plan

Doc fix. Tried the new documented way and it worked.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jcox retitled this revision from to Updated the docs so chatbots can use the Conduit API.
jcox updated this object.
jcox edited the test plan for this revision. (Show Details)
epriestley added a reviewer: epriestley.

I think you can drop all references to conduit.user too if you want, should be fully obsoleted by conduit.token.

You could also reasonably remove the code which actually uses conduit.user, although this probably isn't worth the hassle since it'll probably break some users. Some vaguely related discussion at the bottom of T4377.

resources/chatbot/example_config.json
17–18

This can probably be removed, too.

This revision is now accepted and ready to land.Aug 24 2016, 10:54 PM

(That is, old login was user + cert, new login is token-only, I believe.)

jcox edited edge metadata.
  • Removed references to conduit.user from the docs.
This revision was automatically updated to reflect the committed changes.