Introduces the Flamingock CLI, a command-line tool that enables running Flamingock process independently from the normal application lifecycle.

Execution Model

The CLI operates by spawning the user's application as a subprocess with a controlled configuration:

1. The CLI packages and executes the user's Spring Boot application JAR
2. It activates the flamingock-cli Spring profile, which triggers Flamingock to run in CLI mode
3. Once the changes are applied, the application shuts down automatically

This approach ensures that changes run in the exact same environment as production, using the same dependencies, configurations, and connection settings defined in the application.

Bean Control Annotations

To optimize CLI execution and avoid loading unnecessary components (web servers, schedulers, message listeners, etc.), two new annotations are provided:

Example usage:

@Component
@FlamingockCliExcluded
public class KafkaConsumer {
    // Not loaded during CLI execution
}

@Configuration
public class AppConfig {

    @Bean
    @FlamingockCliExcluded
    public WebServer webServer() {
        // Excluded during CLI execution
    }

    @Bean
    @FlamingockCliOnly
    public DataSource minimalDataSource() {
        // Only loaded during CLI execution
    }
}

These annotations are meta-annotations wrapping Spring's @Profile, so they integrate seamlessly with existing Spring profile mechanisms.