L3D generates identical config_split config for stage and production

Hi, we make extensive use of drupal/config_split in our projects, but we’ve noticed that L3D generates the same config_split configuration for both stage and production environments. This causes issues when we need different configurations on stage and production.

In lakedrops/drupal-environment, we have the following in templates/settings.local.php.twig:

$config['config_split.config_split.develop']['status'] = {{ live ? 'FALSE' : 'TRUE' }};
$config['config_split.config_split.live']['status'] = {{ live? 'TRUE' : 'FALSE' }};

This results in:

- local development:
$config['config_split.config_split.develop']['status'] = TRUE;
$config['config_split.config_split.live']['status'] = FALSE;
So it works as expected.

- stage environment:
$config['config_split.config_split.develop']['status'] = FALSE;
$config['config_split.config_split.live']['status'] = TRUE;

- production environment:
$config['config_split.config_split.develop']['status'] = FALSE;
$config['config_split.config_split.live']['status'] = TRUE;

The question is whether the staging environment should have develop = true and live = false instead.

In other words:

1. Is this behavior as designed?
2. Should we use .lakedrops.yml to customize the config_split config for the stage environment?
3. Or would it make more sense to change this behavior in L3D to generate different config_split configurations for staging and production?

Thanks in advance for any clarification!