Skip to content

fix(build): the minio plugin fragment joins a project's stack only with MinIO intent (D-0702) - #910

Merged
acamarata merged 1 commit into
mainfrom
fix/plugin-fragments-minio-intent-d-0702
Oct 20, 2026
Merged

acamarata merged 1 commit into
mainfrom
fix/plugin-fragments-minio-intent-d-0702

Conversation

@acamarata

Copy link
Copy Markdown
Collaborator

Closes debt row D-0702.

The minio plugin is installed machine-wide (~/.nself/plugins). In v1.5 every project built on the machine merged its compose fragment: a _minio container with an empty volume even with MINIO_ENABLED=false, and two running projects clashed on 127.0.0.1:9000.

Fix: plugin discovery takes a project filter; compose.PluginFragmentWanted leaves the minio fragment out unless ActiveStore picks the plugin (v1.5 with MinIO intent). v1.4 output is unchanged, behind a compat.V15(P7-PLUG-60) marker; the Compat-V15 wiki table is regenerated. Other plugins merge as before.

Test: real Build over a plugin dir with minio and a control plugin, v1.4/v1.5 x intent on/off, reading the written compose manifest. Two mutants (predicate returns true; wiring removed) fail the v1.5 intent-off case.

…th MinIO intent (D-0702)

The minio plugin is installed machine-wide, so in v1.5 every project built on
the machine got a <project>_minio container with an empty volume, and two
running projects clashed on 127.0.0.1:9000. Plugin discovery now takes a
project filter; compose.PluginFragmentWanted keeps the fragment out unless
ActiveStore picks the plugin. v1.4 output is unchanged (compat marker).
@acamarata
acamarata merged commit 668126a into main Oct 20, 2026
33 of 35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant