-
Notifications
You must be signed in to change notification settings - Fork 131
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
97f64b2
commit f59f8ba
Showing
4 changed files
with
37 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -52,3 +52,4 @@ proto | |
quantiles | ||
Config | ||
Grafana | ||
GitHub |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,30 @@ | ||
--- | ||
title: "API Keys in Production" | ||
description: "How to use NativeLink Cloud API keys in production" | ||
pagefind: true | ||
--- | ||
|
||
## GitHub Actions | ||
GitHub Repository Secrets is the recommended way | ||
to store your NativeLink Cloud API keys | ||
for use with GitHub Actions. | ||
|
||
[GitHub Repository Secrets Tutorial](https://docs.github.com/en/actions/security-guides/using-secrets-in-github-actions#creating-secrets-for-a-repository) | ||
|
||
They can be access via the secrets context i.e. | ||
``` | ||
${{ secrets.YourSecretKeyName }} | ||
``` | ||
|
||
:::note | ||
If your repository uses forks for pull requests (PRs), note that the secrets | ||
context isn't accessible from PRs originating from forks. To address this, | ||
we will soon introduce Read-Only keys. | ||
|
||
Read-Only keys can be used for PRs and stored in the vars context. For | ||
merge-to-main actions, use a Read/Write key stored in the secrets context. | ||
::: | ||
|
||
If you need info on setting up API keys for different CI environments, ask in | ||
the [Slack channel](https://nativelink.slack.com/join/shared_invite/zt-281qk1ho0-krT7HfTUIYfQMdwflRuq7A#/shared-invite/email) | ||
or open an issue on our [GitHub](https://github.com/TraceMachina/nativelink). |