Describe the bug
When running plumber config analyze --config /path/to/.plumber.yaml a configuration warning is thrown.
The strange thing is that the .plumber.yaml file has been automatically generated using command plumber config init using the wizard.
To Reproduce
plumber config init
Expected behavior
No warning for this giltab.controls
Screenshots
Configuration validation warnings:
- Unknown control in gitlab.controls: "containerImagesMustBePinnedByDigest". Did you mean "containerImageMustNotUseForbiddenTags"?
Relevant versions and configuration files
- OS: Windows
- Gitlab Version (self managed + tier) 19.2.4
- Plumber version
0.4.40, also seen in v0.4.39
- Your
.plumber.yaml
# Plumber configuration (https://github.com/getplumber/plumber)
# Generated by: plumber config init
version: "2.0"
gitlab:
controls:
containerImageMustNotUseForbiddenTags:
enabled: true
tags:
- latest
- dev
- development
- staging
- main
- master
containerImagesMustBePinnedByDigest:
enabled: false
...
Note: If you submit a PR for this bug, please keep "Allow edits from maintainers" enabled so we can collaborate on the fix more easily.
Describe the bug
When running
plumber config analyze --config /path/to/.plumber.yamla configuration warning is thrown.The strange thing is that the
.plumber.yamlfile has been automatically generated using commandplumber config initusing the wizard.To Reproduce
plumber config initExpected behavior
No warning for this
giltab.controlsScreenshots
Relevant versions and configuration files
0.4.40, also seen inv0.4.39.plumber.yaml