Skip to content

Reference

This page documents exact behavior. Open the reference overview

Profiles Reference

Reference

This page covers the exact profile selection and storage rules. Use it when you already know what profiles are and need the precise mechanics.

Selection order

The active profile is resolved in this order:

  1. --profile
  2. ENVCTL_PROFILE
  3. config default_profile
  4. local

Storage rules

  • values.env is the canonical file for the implicit local profile
  • explicit profiles are stored as profiles/<name>.env
  • local does not use profiles/local.env
  • explicit profiles must exist before use

Commands

list

envctl profile list

Shows the available profiles for the current project.

create

envctl profile create dev

Creates a new explicit profile.

copy

envctl profile copy dev staging

Copies one profile into another.

remove

envctl profile remove staging

Removes one explicit profile.

path

envctl profile path dev

Shows the physical path for a profile file.

Rules

Profiles follow a few important rules:

  • profiles do not change the contract
  • profiles do not inherit from each other
  • profiles are local only
  • add, set, unset, and fill target the active profile only
  • remove removes the key from the contract and all persisted profiles

Profiles concept

Go back to what profiles mean in the model.

Read about profiles

Profiles guide

See the workflow for creating, filling, copying, and removing profiles.

Open profiles guide

Configuration reference

Reconnect selection rules to the config defaults that participate in them.

Open configuration reference