SovereignCloudStack / SovereignCloudStack/standards
Refine item #4 in SCS-0004
@depressiveRobot is already working on this.
Since Feb 19, 2026.
- Dominant language
- Python
- Stars
- 47
- Forks
- 38
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 8
Description
IMO, the deletion time is not clear, but could be very important for providers, especially, if test suite failed frequently for a specific certificate scope and version.
the page will be reanimated and reused if, within this timeframe, a new certificate is issued for the same scope and the same cloud.
Does this means, that the entire history of all test results for all previous certificate version is refreshed in case a new version is issued? E.g. SCS-compatible IaaS v1.0, SCS-compatible IaaS v2.0, SCS-compatible IaaS v3.0, SCS-compatible IaaS v4.0 and SCS-compatible IaaS v5.0 is still visible in Compliance Monitor, in case SCS-compatible IaaS v6.0 is issued?
IMO, we should be more precise in deletion time, e.g. "... the last three version (if present) will be visible, in case a new certificate version is issued. Test results older then three past version will be deleted 3 month after expiring date.
Originally posted by @anjastrunk in https://github.com/SovereignCloudStack/standards/pull/781#discussion_r1940683651
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.