Skip to main content

Flamingock library configuration

Flamingock provides flexible configuration options to support a variety of environments and workflows — from local setups to cloud-native distributed systems.

Configuration is divided into two distinct scopes:

  • Setup configuration defines how Flamingock discovers and organizes change units. This is configured using the @Flamingock annotation.

  • Runtime configuration includes optional parameters such as locking, metadata, author, etc., and can be provided via builder or (depending on the environment) a file.

What you can configure

AreaDescriptionLink
⭐ Setup & stagesOrganize changes into ordered stages - EssentialSetup & stages
⭐ Target systemsConfigure target systems for your changes - EssentialTarget systems
⭐ Audit storeConfigure audit storage - EssentialAudit stores
Global dependency injectionDependency injection to Changes and environmentContext and dependencies
Cloud EditionCloud-specific setup: token, env, serviceCloud Edition
Framework integrationIntegration with frameworks (currently Spring Boot)Spring Boot integration
LockDistributed locking and timing optionsLock configuration
ExtraMetadata, default author, enable/disableAdditional configuration

Each of these topics is explained in its own section.

Applying runtime configuration

Runtime configuration (everything except the pipeline) can be applied in the following ways:

Runtime environmentBuilderFile
Standalone❌ (coming soon)
Springboot✅(framework native)
info

You can combine both approaches. If a property is defined in both, the builder value takes precedence.

Next steps

Start with the essential configurations marked with ⭐, then explore additional options based on your needs:

Essential configurations (start here)

Additional configurations

Choose your edition