Environment Variables

Environment variables hold non-secret configuration for your client organisation. Reference them in cloud-init user data profiles with Jinja: {{ env.APP_ENV }}.

Manage them at /organization/environment-variables under Orchestration → Environment Variables.

Typical uses

Values are visible in the UI and API: store passwords and tokens in Secrets instead.

Using env vars in profiles

After creating a variable, reference it in a profile:

#cloud-config
write_files:
  - path: /etc/myapp/env
    content: APP_ENV={{ env.APP_ENV | tojson }}

NodeRings validates profiles when you save them. Missing env.* references produce warnings (the profile can still be saved).

Reserved keys

Do not use keys that collide with built-in provision variables (vm, vm_network, password, env, secret, and similar). Create or update will be rejected if the key is reserved.

Next

• Secrets
• Cloud-init user data
• Virtual machines: choose a profile at launch