SovereignCloudStack / SovereignCloudStack/standards
[BUG] Invalid entry in config.toml results in broken tests for all
Open
@mbuechse is already working on this.
Since Jul 20, 2026.
bug
- Dominant language
- Python
- Stars
- 47
- Forks
- 38
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 8
Description
As #1251 has shown, a broken/wrong config entry in the compliance monitor results in „red lights” for all tested clouds. This should not have an effect. Is there a way to run a check within the GitHub actions maybe?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.