| 1 | # Secret Management
|
| 2 |
|
| 3 | One of the key benefits Atomist provides is management of
|
| 4 | secrets. Secrets are resolved per organization or *individual user* in
|
| 5 | the event of a command handler. This is an important capability, as
|
| 6 | often automations all run as the same user, making for a poor audit
|
| 7 | trail.
|
| 8 |
|
| 9 | Secrets are injected via decorators.
|
| 10 |
|
| 11 | For example, the following will cause an instance variable to be
|
| 12 | populated before the `handle` method of a handler is invoked:
|
| 13 |
|
| 14 | ```typescript
|
| 15 | @Secret(Secrets.ORG_TOKEN)
|
| 16 | public githubToken: string;
|
| 17 | ```
|