users no longer have an arcrc file with the {"hosts": {"your-hostname.com/api": {"user": "bot-username", "cert": "yourlongasscertgoeshere"}}} template, and setting a certificate to a bot account is not explicitly documented.
Description
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Duplicate | None | T7288 configuring certificates for bots is hard/confusing | ||
Resolved | epriestley | T5955 Refactor Conduit auth to be stateless, token-based, and support wire encodings | ||
Resolved | btrahan | T5603 Implement a separate "Can Leave Project" policy |
Event Timeline
Comment Actions
In a post-T5955 world, this should probably just become something like:
arc call-conduit method.name --conduit-uri https://phabricator.example.com --conduit-token api-asdb9asdy9b8ab98adsh
But since curl can pretty much work fine once tokens are slightly farther along, we may not even really need this stuff.