Kameleoon Environments are used to organize and align with distinct, segregated platforms or spaces within your technical architecture where your application(s) are deployed, tested, and run from. Once set up, environments offer a controlled and systematic approach to development, deployments and QA across multiple environments.
When you create a new project, Kameleoon will automatically create 3 feature environments for you: Production, Staging and Development. These environments are intended to iterate, test, and refine software in a structured manner, minimizing risks and ensuring a seamless, safer release cycle.
Customizing Environments
Start by navigating to the Set Up menu and click Environments to see your current project environments.
You’re free to customize these environments (except Production, which can only be renamed) – or, create any additional ones you need. If you have a need for additional environments, simply click Add an Environment.
Enter a name and key for your new environment, and save to confirm. You can also reorder the environments to your preference.
You will now see it in the list of your environments within the Rollout Planner, in the same order as you arranged them in the Environments page.
To finish your setup, you’ll have to also point these environments to your appropriate infrastructure using the instructions in the “Note” below.
Scope of Environments
You will be able to use your feature variables, variations and goals across all of your environments, so you don’t need to recreate them individually for each environment when configuring a feature. However, Environments are uniquely global to the entire project, and not just localized to the flag you’re working in. Therefore, any changes you make on the Environments page will also take effect on all other feature flags for that specific project, so keep that in mind when editing or removing environments.
On the Feature Flags dashboard, you’ll be able to filter flags quickly by Project and Environment Key. Some keys may have been used across multiple projects, in which case you can view those projects by hovering over the ⓘ icon next to the key.
Note: To use Kameleoon’s multi-environments feature flagging, you will have to use the parameter named “environment” within the YAML configuration file to define the environment key. In the case there is no environment specified within your YAML file, the configuration associated with the Production environment from your feature flag edit page will be applied by default. Read your SDK’s documentation to learn more.
Once done, you can now start developing, testing and delivering your features using a seamless multi-environment setup.
