Page MenuHomePhabricator

Allow API tokens to be added to arcrc
AbandonedPublic

Authored by cinek on Oct 14 2015, 12:40 PM.
Referenced Files
F19028424: D14275.diff
Mon, Nov 24, 3:35 PM
F18854606: D14275.id34457.diff
Nov 1 2025, 12:23 AM
F18826016: D14275.id34457.diff
Oct 24 2025, 2:00 AM
F18785879: D14275.diff
Oct 14 2025, 1:56 PM
F18712780: D14275.id.diff
Sep 29 2025, 5:32 AM
F18506598: D14275.id.diff
Sep 5 2025, 1:37 AM
F18499209: D14275.diff
Sep 4 2025, 7:31 PM
F17899869: D14275.diff
Jul 29 2025, 8:48 AM
Subscribers

Details

Summary

When generating conduit tokens for bot users, one gets an API token with prefix
"api-". With this trivial fix arc install-certificate allows such tokens to
be set up in ~/.arcrc.

This commit fixes T8143.

Test Plan
  • Started arc install-certificate.
  • Generated API token at https://phabricator.domain.org/settings/panel/apitokens/.
  • Pasted API token to arc prompt.
  • Verified that API token showed up in ~/.arcrc.

Diff Detail

Repository
rARC Arcanist
Branch
fixT8143
Lint
Lint Passed
Unit
Tests Passed
Build Status
Buildable 8274
Build 9477: arc lint + arc unit

Event Timeline

cinek retitled this revision from to Allow API tokens to be added to arcrc.
cinek updated this object.
cinek edited the test plan for this revision. (Show Details)
cinek added a reviewer: epriestley.
epriestley edited edge metadata.

It's intentional that you can't add api- tokens via this workflow. Use --conduit-token. I don't intend to bring this change or any similar change upstream.

This revision now requires changes to proceed.Nov 2 2015, 4:42 PM

It's OK. I can still add the API tokens for bots manually to the configuration. I don't like users to see them in ps output.