👋 Email us at [email protected] with questions or feedback. We'd love to hear from you. If you have an account with RWX, view your support page for access to support via Slack.
Circle has two approaches to setting environment variables: context and project. We recommend using contexts as it allows you to share the token across multiple workflows.
On your organization settings page, click on "Contexts"
Click on "Create Context" and give it a name. In our documentation, we use a context named "rwx". If you use that name, it'll be easier to copy/paste our example workflows
Click on the context, then click "Add Environment Variable"
Enter RWX_ACCESS_TOKEN in the "Environment Variable Name" field
Paste the Access Token into the "Value" field
GitLab
You can set environment variables in GitLab's variable settings. For ease of sharing it across projects, we recommend setting it at the instance-level if self-hosting GitLab or at the group level if using hosted GitLab. Here's how to do it for on a group:
On your group's page, hover over "Settings" in the menu on the left and click on "CI/CD"
Click on "Variables" to expand it, and then click on "Add Variable"
Enter RWX_ACCESS_TOKEN in the "Key" field
Paste the Access Token into the "Value" field
Leave "Type" set to "Variable" and "Environment scope" set to "All"
Ensure that only "Mask variable" is checked ("Protect variable" flag will prevent the CLI from working properly for feature branches. "Expand variable reference" is unnecessary.)
Recovering an Access Token
We do not store Access Tokens in our system; we only save digests.
Therefore, we cannot recover a lost Access Token.
If you misplaced a token, generate a new one.
Rotating an Access token
You can have as many Access Tokens as you'd like. To rotate a token: