Environment Variables


Environment variables are a crucial aspect of software development and deployment. They are used to store sensitive information or configuration settings that shouldn’t be hardcoded into the codebase.

One of the primary reasons to use environment variables is to enhance the security of your project. Sensitive information such as API keys, database credentials, or access tokens can be easily compromised if they are hardcoded in your codebase.

By using environment variables, you can keep this sensitive information separate from the code and limit access to authorized individuals or systems. This reduces the risk of accidental exposure or unauthorized access to critical data.

Environment variables enable greater flexibility in configuring your application. Instead of modifying code or recompiling your application to update settings, you can simply change the values of the environment variables.

This makes it easier to deploy your application across different environments (development, staging, production) or when using different providers (such as cloud platforms), as each environment can have its own set of variables.

Environment variables contribute to the portability of your application. By abstracting configuration details away from the code, you can easily move your application between different environments or platforms without modifying the codebase. This is particularly useful when scaling your application or deploying it in different hosting environments.

Environment variables promote collaboration among team members. Since sensitive information isn’t exposed directly in the codebase, it’s safer to have more than one developer working on the same project.

By excluding sensitive information from the codebase, you can avoid committing secrets to version control systems. This prevents secrets from being inadvertently leaked when sharing code repositories or during code reviews. Instead, only the configuration templates or placeholders for environment variables are committed, ensuring the security of sensitive information.

In many cases, organizations need to adhere to compliance standards that regulate the handling of sensitive data. By using environment variables, you can meet these compliance requirements by ensuring sensitive information is properly protected, controlled, and auditable.

Environment variables on the Azion platform

Section titled Environment variables on the Azion platform

You can manage your environment variables trough the Azion API

for previous versions of azion cli 1.x.y

The command variables is available and can be used to manage your environment variables using Azion CLI.

Learn more about the command on Variables command and its subcommands

Environment Variables and Edge Functions

Section titled Environment Variables and Edge Functions

You can retrieve the value of your configured environment variable inside an edge function by making use of the Azion.env.get() interface, passing its key. Example:

const apiToken = Azion.env.get('API_SERVICE_TOKEN');

Learn more about the Environment Variables interface.

These are the default limits:

Keys100 per clientEach account can have a maximum of 100 defined variables.
Value32 kBThe maximum size of a value is 32 kB.