Expand description
bynk login, bynk logout and bynk org (first-party registry R3.1,
#2378): the client side of the account API the hosted registry serves
beside its publish API (R3, #2363).
login runs GitHub’s device flow through the registry and keeps the
account token (bynka_…) in the credentials file’s [accounts.<name>],
apart from the publish token bynk publish reads from
[registries.<name>] token. org token mint --save writes a new publish
token into the organisation’s own slot,
[registries.<name>.organisations.<org>] token (R3.2, #2383).
Structs§
- Mint
- What
token mintis asked for. - Target
- Which registry a command talks to:
--registry, else the one the organisation routes to in the project atproject(loginandlogouthave no organisation, and default to the first-party registry).
Functions§
- claim
- Claim
org, first come (blockholds it without publishing; an operator names theowner). - login
- Sign in to
target’s registry through GitHub’s device flow, and keep the account token. - logout
- Sign out of
target’s registry: end the session on the server, and forget it here. - member_
add - Add the GitHub user
logintoorg. - member_
remove - Remove a member from
org, by GitHub login or numeric id. - override_
variable BYNK_ACCOUNT_<NAME>_TOKEN. NotBYNK_REGISTRY_<NAME>_ACCOUNT_TOKEN, which is registry<name>-account’s publish token.- set_
blocked - Block or unblock
org. - show
- Print
org: its owner, members, whether it is blocked, and its tokens (never the tokens themselves).jsonprints the API’s answer as it is. - token_
mint - Mint a publish token for
org: printed once on stdout, or saved wherebynk publishreads it (decision E). - token_
revoke - Revoke one of
org’s publish tokens, by its id (or a unique prefix of it, asorg showprints it).