Skip to content

Commit 6f21e10

Browse files
Add page dedicated to compliance monitor (#398)
* Add page dedicated to compliance monitor Move corresponding part from overview.md to that page * adjust mentions of compliance monitor --------- Signed-off-by: Matthias Büchse <matthias.buechse@alasca.cloud> Signed-off-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com> Co-authored-by: Marvin Frommhold <depressiveRobot@users.noreply.github.com>
1 parent 6317d73 commit 6f21e10

5 files changed

Lines changed: 14 additions & 6 deletions

File tree

populateClouds.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,8 @@ async function insertCloudTable(pathIn, pathOut) {
1111
}
1212

1313
insertCloudTable(
14-
`standards/certification/overview.template.md`,
15-
`standards/certification/overview.md`
14+
`standards/certification/monitor.template.md`,
15+
`standards/certification/monitor.md`
1616
).catch((e) => {
1717
console.log(e)
1818
})

sidebarsStandards.js

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,11 @@ const sidebars = {
1010
id: 'certification/overview'
1111
},
1212
items: [
13+
{
14+
type: 'doc',
15+
label: 'Compliance Monitor',
16+
id: 'certification/monitor'
17+
},
1318
{
1419
type: 'doc',
1520
label: 'Compliance Check Pipeline',
Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
<!-- markdownlint-disable -->
2+
# SCS Compliance Monitor
3+
4+
<!--CLOUDS-->

standards/certification/overview.template.md renamed to standards/certification/overview.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,3 @@
1-
<!-- markdownlint-disable -->
21
# Certification
32

43
SCS provides a certification framework with various [scopes](https://docs.scs.community/standards/scopes/).
@@ -23,4 +22,4 @@ The standard [SCS-0007](https://docs.scs.community/standards/global/scs-0007) de
2322

2423
## Compliant cloud environments
2524

26-
<!--CLOUDS-->
25+
See the [SCS Compliance Monitor](https://docs.scs.community/standards/certification/monitor) for a list of compliant cloud environments.

standards/certification/pipeline.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
# SCS Compliance Check Pipeline Manual
22

33
The SCS compliance check suite runs automated tests, generates a signed report for the run, and feeds it to
4-
the compliance monitor. Roughly speaking, this process has to be performed daily, for instance, using a
4+
the [SCS Compliance Monitor](https://docs.scs.community/standards/certification/monitor). Roughly speaking, this process has to be performed daily, for instance, using a
55
continuous-integration "pipeline".
66

77
Providers of public clouds do not need to use their own pipelines; those clouds can be tested via the
@@ -35,7 +35,7 @@ to be used for purposes other than compliance testing (such as the
3535
Github first and then clone the fork.
3636

3737
3. Add your subject to the results table. This is necessary so your subject shows up in the
38-
[compliance monitor web-site](https://compliance.sovereignit.cloud/page/table). Add the following lines
38+
compliance monitor. Add the following lines
3939
(substituting all-caps parts except `HM`) to
4040
[compliance-monitor/templates/overview.md.j2](https://github.com/SovereignCloudStack/standards/blob/main/compliance-monitor/templates/overview.md.j2):
4141

0 commit comments

Comments
 (0)