To avoid specifying
--project-name in every
invocation, aperturectl can use a configuration file located in
The location of this file can be overridden by the
--config option (with the command-line option having higher
When any explicit flag related to controller location (e.g.,
--project-name) is used, the value from the
configuration file is ignored for the flag.
If the configuration file is not specified nor present at the default location,
aperturectl will try to find the controller at the local Kubernetes cluster (as
--kube flag were passed).
The aperturectl configuration file uses the following TOML syntax:
url = "ORGANIZATION_NAME.app.fluxninja.com:443"
project_name = "PROJECT_NAME"
api_key = "PERSONAL_API_KEY"
ORGANIZATION_NAME with the Aperture Cloud organization name and
PERSONAL_API_KEY with the Personal API key linked to the user. If a Personal
API key has not been created, generate a new one through the Aperture Cloud UI.
Refer to Personal API Keys for additional information.
You can create multiple configuration files and use
environment variable to switch between different projects and organizations.