How to customized PropertySource on some subcommand

[tchiotludo]

I've an application with subcommands like that :

@Command(name = "topcmd", subcommands = {SubCmd1.class, SubCmd2.class}) 
class TopCommand implements Callable<Object> { 

    public static void main(String[] args) {
        PicocliRunner.execute(TopCommand.class, args); 
    }
    //...
}

I want to be able to add some PropertySource (custom configuration) for only 1 subcommands (for example SubCmd2.class will add a configuration "myapp.myconfig": "foo" only when running te command from SubCmd2).

I don't think it's possible for now ?

The only solution I see is to used this signature when init Picocli :

public static <C extends Callable<T>, T> T call(Class<C> cls, ApplicationContext ctx, String... args) {

instead of simple on PicocliRunner.call(App.class, args); in order to provide some configuration directly in ApplicationContext but this will need to parse the String[] args to determine the current command, that is not really easy and can be buggy since it's not parse by picocli.

[guillermocalvo]

@tchiotludo I'm not 100% sure I get what you're trying to achieve 🤔

You want to define a config property myapp.myconfig but only if SubCmd2 is running. Is that correct? What's preventing you from defining this property and then making other subcommands simply ignore it? Why is it so important that the property is not defined unless a specific command is running? I'd like to understand what's the actual use case, and why it cannot be done some other way.

[tchiotludo]

In my special case, I need to inject custom datasources properties for a specific command, this will configure an h2 database for a command automatically.

You could find an implementation here :

• declare custom properties
• inject theses properties

[sdelamo]

If remkop/picocli#2079 got implemented, I think we could do something to simplify it.

[remkop]

@tchiotludo is this solution feasible for you?

[tchiotludo]

@remkop it's exactly what I do here.

In a better world, I would like to have a better integration in micronaut, maybe an annotation @Property(name = "foo.bar", value = "stuff") that will auto inject the configuration parameter on that command only like the Junit integration?