Show plugin settings in system property list - #1696
Conversation
97167bb to
4cfca1e
Compare
4cfca1e to
b67d8b0
Compare
|
Gentle ping on this one (open since June 11). It implements #607 — It's self-contained (a new |
|
Hi @katiewasnothere — gentle follow-up on this when you have a chance. It closes #607 by surfacing |
b67d8b0 to
b8f9af5
Compare
|
@katiewasnothere Gentle ping on this when you have a chance. It closes #607 — No CI has run on the fork branch yet; happy to help unblock that if needed. Thanks! |
b8f9af5 to
4bfd9a7
Compare
|
hey @katiewasnothere (and @jglogan for the CI bit). just rebased this onto main. could you approve the workflow so the checks can run? happy to take a review whenever you have a sec after that. |
4bfd9a7 to
d882f3d
Compare
Signed-off-by: amarkdotdev <amarkdotdev@users.noreply.github.com>
d882f3d to
6e05468
Compare
|
@katiewasnothere @jglogan rebased again. Could one of you approve the CI workflow and take a look when you have time? |
Type of Change
Motivation and Context
container system property listshowed core system configuration but omitted plugin-scoped values from[plugin.*]sections. This change includes those plugin settings in TOML and JSON output, using the same daemon-reported app-root and install-root config files as the core system properties. Nested plugin values preserve the existing first-match-wins layering behavior.Fixes #607
Testing
Commands run locally:
swift test --filter PluginPropertiesTestsswift test --filter ContainerCommandsTests