Modules are groupings of Products that are often installed together to Environments.
Modules allow you to install many Products to an Environment at once rather than install each Product individually. When you create a Module, you will specify configuration that will be applied to every installation of the Module.
Learn more about managing Modules.
The Entities in a Module are the Products and configuration that are included in the Module. When you install a Module, Apollo will install each Entity in the Environment.
Variables allow you to add flexibility to your Module. Instead of using pre-defined values in the Entity definition and Module configuration, you can use a variable. The value of the variables will be set at Module installation rather than Module creation.
You can use Module variables in every section of the Entity definition, including the configuration overrides.
Composite Modules allow you to create a Module from other existing Modules. This enables you to manage complex configurations by breaking them down into smaller, reusable components.
Learn more about Composite Modules.
Each version of a Module is published as a Release (similar to Product Releases) and are identified by Maven coordinates. Module Releases support Release Channels and recalls.
Module installations track Release Channels, and Apollo will only propose updates to Releases that have been promoted to the installation's tracked channel. By default, installations follow the Environment's default Release Channel, but you can override this for individual installations.
Recalling a Module Release prevents Apollo from proposing updates to that version and cancels any open change requests that would update installations to that version.
Unlike with Product recalls, Apollo will not automatically move installations off a recalled Module Release.