| 1 | package updatewords |
| 2 | |
| 3 | func init() { |
| 4 | add( |
| 5 | Draft{ID: "settings.evidence.no-record", |
| 6 | Text: "no promotion record: pick a newer build, or ask an operator to authorize this one", |
| 7 | Context: "Why a pin, an install request or a recovery onto an older build was refused: the build was promoted before promotion records existed, or never promoted. Shown in carlos instances list, on the instance page, and returned by the console when a pin is set."}, |
| 8 | Draft{ID: "settings.authorize.intro", |
| 9 | Text: "Authorize %s %s with this manifest:", |
| 10 | Context: "First line of carlos releases authorize, above the digests. App and version."}, |
| 11 | Draft{ID: "settings.authorize.manifest-row", |
| 12 | Text: " manifest %s", |
| 13 | Context: "The manifest's sha256, the one digest the signed record will carry."}, |
| 14 | Draft{ID: "settings.authorize.artifact-row", |
| 15 | Text: " %s %s", |
| 16 | Context: "One line per file of the build: its platform (or site) and its sha256, so the person can check them against what they built."}, |
| 17 | Draft{ID: "settings.authorize.prompt", |
| 18 | Text: "Sign a promotion record for exactly these bytes? Type yes to continue: ", |
| 19 | Context: "Asked after the digests. Anything but yes signs nothing. --yes skips it."}, |
| 20 | Draft{ID: "settings.authorize.done", |
| 21 | Text: "authorized %s %s: it can now be pinned and recovered on any box", |
| 22 | Context: "Printed after a record is signed. App and version."}, |
| 23 | Draft{ID: "settings.authorize.already", |
| 24 | Text: "%s %s already has a promotion record for these bytes; nothing to sign", |
| 25 | Context: "Printed when the build already has a record with the same digest."}, |
| 26 | Draft{ID: "settings.authorize.aborted", |
| 27 | Text: "nothing signed", |
| 28 | Context: "Printed when the person did not type yes."}, |
| 29 | Draft{ID: "settings.authorize.changed", |
| 30 | Text: "the manifest of %s changed since it was shown. Nothing was signed. Run the command again", |
| 31 | Context: "Returned when someone reshipped the version name between showing the digests and the confirmation. %s is the version."}, |
| 32 | Draft{ID: "settings.authorize.root-only", |
| 33 | Text: "authorizing a build needs the deployment's root key. A scoped key cannot do it", |
| 34 | Context: "Returned by carlos releases authorize against a bucket directly with a scoped CARLOS_RELEASE_KEY."}, |
| 35 | Draft{ID: "settings.authorize.not-shipped", |
| 36 | Text: "%s has not been shipped, or its manifest cannot be read", |
| 37 | Context: "Returned when the version named does not exist. %s is the version."}, |
| 38 | Draft{ID: "settings.authorize.no-key", |
| 39 | Text: "this console has no release key, so it cannot sign a promotion record", |
| 40 | Context: "Returned by the console's authorize door when the console was started without the deployment's release key. Shown by carlos releases authorize."}, |
| 41 | Draft{ID: "settings.authorize.write-failed", |
| 42 | Text: "could not confirm the promotion record was written. Run the command again to check", |
| 43 | Context: "Returned by the console's authorize door when the record write failed or its outcome is unknown. Running the command again reports \"already\" if the record was written, or signs it. Shown by carlos releases authorize."}, |
| 44 | Draft{ID: "settings.authorize.usage", |
| 45 | Text: "usage: carlos releases authorize [--app <a>] [--account <sqid-or-name>] [--yes] <version>", |
| 46 | Context: "Printed when carlos releases authorize is run with the wrong arguments."}, |
| 47 | Draft{ID: "settings.authorize.flag-yes", |
| 48 | Text: "sign without asking", |
| 49 | Context: "Help text for the --yes flag of carlos releases authorize."}, |
| 50 | Draft{ID: "settings.authorize.flag-console", |
| 51 | Text: "console origin to authorize through (API mode only; default: the only logged-in one)", |
| 52 | Context: "Help text for the --console flag of carlos releases authorize."}, |
| 53 | Draft{ID: "settings.authorize.docs", |
| 54 | Text: "`carlos releases authorize <app> <version>` is for operators. It shows a build's manifest and file digests and, when you type yes, signs a promotion record for exactly those bytes. Every promotion writes one; this is for a build promoted before records existed, so an instance can be pinned to it or recovered onto it on a box that does not already have it.", |
| 55 | Context: "The CLI docs page's paragraph about carlos releases authorize."}, |
| 56 | ) |
| 57 | } |
| 58 | |
amadan