Secrets & Hurl variables

Almost every sufficiently complex script will at some point require you to pass an authentication token to an API request. For example, the following script uses the Hurl variables CLOUDFLARE_TOKEN and CLOUDFLARE_ACC_ID to successfully call the API to list our Cloudflare D1 databases.

list-d1-databases.hurl

GET https://api.cloudflare.com/client/v4/accounts/{{ CLOUDFLARE_ACC_ID }}/d1/database
Authorization: Bearer {{ CLOUDFLARE_TOKEN }}
HTTP 200

Skybear.NET provides support for securely storing Hurl variables in your account.

All Hurl variables in your account are passed as environment variables in your scripts making it easy to use them with the name you specified during their creation.

Encryption everywhere

All the Hurl variables stored in your Skybear.NET account are encrypted inside our application servers, before being send to our cloud providers databases that also provide encryption at rest on their side.

Shared responsibility

All Hurl variables are being treated as sensitive secrets inside the Skybear.NET platform. Never logged or stored in plaintext.🔐 Script Run reports are also encrypted since variables can be part of HTTP headers.

How your scripts use them is up to you though. Don’t include them in your requests unless necessary.

Visit https://www.skybear.net/account/secrets to manage your Hurl variables and add new ones.

The following screenshot is an example of how it looks like:

If you already have local .env files with Hurl variables you use in your scripts, you can simply COPY them all and PASTE them in the first input box. All of them will be added automatically.

For example, assume we have the following .env file:

.env

CLOUDFLARE_ACC_ID=ajdhasudhoasuihde8wh83
CLOUDFLARE_TOKEN=837geydbhc98765drtfvybuhdfghj837geydbhc98765drtfvybuhdfghj837geydbhc98765drtfvybuhdfghj
DEMO_AUTH_TOKEN=something-something

Copying and pastying these into the form above, we will get the following: