feat: Update documentation surrounding CI and API keys#516
feat: Update documentation surrounding CI and API keys#516
Conversation
| ## Migrating from `shorebird login:ci` | ||
|
|
||
| The `shorebird login:ci` command is deprecated. Existing tokens generated by | ||
| `login:ci` will continue to work until March 2027, but we recommend replacing |
There was a problem hiding this comment.
| `login:ci` will continue to work until March 2027, but we recommend replacing | |
| `login:ci` will continue to work until September 2026, but we recommend replacing |
There was a problem hiding this comment.
Yeah I agree on the 6 months timeline. Biggest thing is making sure we end up putting this into multiple customer comms like the newsletter and other emails
cc @dawn-ducky
| The `SHOREBIRD_TOKEN` is a secret and should not be checked in to your source | ||
| control or shared publicly. | ||
| The `shorebird login:ci` command is deprecated. Existing tokens generated by | ||
| `login:ci` will continue to work until March 2027, but new tokens should be |
There was a problem hiding this comment.
| `login:ci` will continue to work until March 2027, but new tokens should be | |
| `login:ci` will continue to work until September 2026, but new tokens should be |
| authenticated. In order to authenticate with Shorebird in CI, you will need to | ||
| generate a CI token. | ||
| Most Shorebird functionality, like creating releases and patches, requires | ||
| authentication. To authenticate in CI, create an API key from the |
There was a problem hiding this comment.
| authentication. To authenticate in CI, create an API key from the | |
| authentication. To authenticate in your CI, create an API key from the |
We kind of need to start talking about a users CI system vs. ours since we have a CI product as well.
| ::: | ||
|
|
||
| Example: | ||
| :::note |
There was a problem hiding this comment.
Feels kinda weird to have 3 callouts in a row.
|
|
||
| export SHOREBIRD_TOKEN="$SHOREBIRD_TOKEN" && shorebird patch android | ||
| ``` | ||
| On Pro and Business plans, you can restrict an API key to **Release & Patch |
There was a problem hiding this comment.
Should this just link to the orgs section that talks about roles instead of duplicating the content?
| - **Full access** — the key has the same permissions as your account. Available | ||
| on all plans. | ||
| - **Release & Patch only** — the key can create releases and patches, but cannot | ||
| manage apps, organizations, members, or billing. Available on Pro and Business |
There was a problem hiding this comment.
Same thing with a link to the orgs/roles section would be good here.
Status
READY
Description
login:ci, and security details.shorebird login:cicommand. Includes a migration callout notinglogin:citokens remain valid until March 2027.