Create Configuration
Creating a new Deployment Configuration means defining a new version interval for a target environment. The following sections describe the three situations in which this happens and explain how CodeNOW pre-populates the values in each case.
First configuration for an environment
When no Deployment Configuration exists for a given environment yet, there is no interval to cover any package version. Any attempt to deploy will fail until at least one configuration is created.
In this case, CodeNOW has no previous configuration to reference, so the new configuration is pre-populated from the component defaults — the configuration values stored with each component's released version in git.
Components with connected service bindings cannot use defaults — a binding only declares the service type, not a specific instance. These must be assigned manually before the configuration can be saved and the application deployed.
Splitting an existing interval
There are two reasons to split an existing interval:
-
Structural configuration change in one or more components — a new application version introduces a change that is incompatible with the existing configuration: a restructured configuration file, a new or removed connected service binding, changed environment variable names, or updated resource requirements. If the change affects a connected service binding, CodeNOW will enforce the creation of a new interval — the configuration cannot be saved without assigning the new binding. For other structural changes it is the user's responsibility to recognize that a new interval is needed.
-
Preserving backward compatibility for a previous package — a deliberate decision to keep an older interval intact so that it remains possible to roll back to a previous package version and deploy it with its original configuration. Without splitting, extending the interval with new values would apply to all packages in the range, including those you might want to roll back to.
In both cases you create a new configuration at the version where the change takes effect. The existing interval is automatically shortened to end just before the new one begins, and the new interval is pre-populated from the existing configuration that covered that version range. You only need to update what actually changed.
Extending to a new version range
When you want to define a distinct configuration for versions beyond the current last interval — for example after a major release that requires different environment-specific values — you create a new configuration starting at that version. The previous last interval is automatically shortened to end there.
CodeNOW pre-populates the new interval from the last existing configuration for that environment.
Configuration Sections
To create a new configuration, select the target environment and the application version that starts the new interval. Each component in the application then exposes three sections that can be edited independently:
| Section | Description |
|---|---|
| Configuration Files | Override configuration files for the component |
| Runtime Configuration | Set instance count and CPU / memory limits |
| Connected Services | Assign service instances to component bindings |
Use the Compare with panel to load a reference configuration from another environment or version side by side while editing.