spl:configurations
Introduction
spl:configurations counts the valid products of a line and shows which features are core, optional or dead. A dead feature, one no product can select, usually points at a contradictory constraint.
splent spl:configurations sample_splent_spl --count
SPL : sample_splent_spl
UVL : /workspace/.splent_cache/spls/sample_splent_spl@v4/sample_splent_spl.uvl
Features : 17
432 valid configuration(s)
Core (always present): auth, public, session_type, settings, theme
Optional: admin, confirmemail, mail, mailhog, nginx, phpmyadmin, profile, redis, reset, session_filesystem, session_redis
Listing every configuration
splent spl:configurations my_spl
SPL : my_spl
UVL : /workspace/splent_spl_my/my_spl.uvl
Features : 4
3 valid configuration(s)
Core (always present): auth
Optional: notes, reports
# Features Size
──────────────────────────────────────────────────────────────────────
1 auth base
2 auth, notes +1
3 auth, notes, reports +2
core optional dead
Without --count it lists them, smallest first. base is the core alone and +N counts the optional features added. Core features show in green, optional in yellow, dead in red.
Over 50 configurations it asks before listing. Over 200 it never lists them, so use --count or add constraints.
Reference
| Option | Description |
|---|---|
--count |
Show the total and the core, dead and optional features, without the list |
--with-sat |
Count with the PySAT backend, which helps in some environments |
Requirements
- Detached mode, with no product selected. A leading
SPLENT_APP=runs one command detached and keeps your selection. flamapy, to analyse the model. The CLI container has it. Elsewhere,pip install splent_cli[uvl].
See also
spl:featureslists the features of the model.product:validatechecks that one product is a valid configuration.