You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
-
# Configuration Service
1
+
# API
2
2
3
3
## Overview
4
4
5
-
The Configuration service is a core component of The Continuous Compliance Framework. It manages all the data and
5
+
The API is a core component of the Continuous Compliance Framework. It manages all the data and
6
6
aggregation for compliance, and agent-collected data.
7
7
8
8
The data structures in the service are heavily based on OSCAL (Open Security Controls Assessment Language), with the
@@ -20,16 +20,16 @@ goal of full support.
20
20
This will also start the required auxiliary services.
21
21
22
22
```shell
23
-
make up
23
+
make up
24
24
# OR podman-compose up -d
25
-
# OR docker compose up -d
25
+
# OR docker compose up -d
26
26
27
27
curl http://localhost:8080
28
28
```
29
29
30
30
### The command line
31
31
32
-
The Configuration Service ships with a built in CLI, which can be used to run administrative tasks within.
32
+
The API ships with a built in CLI, which can be used to run administrative tasks within.
33
33
34
34
Some examples include:
35
35
```shell
@@ -50,15 +50,15 @@ $ go run main.go help # Learn more about all the available commands
50
50
> [!IMPORTANT]
51
51
> Make sure you run `make swag` when first cloning the repository (either locally or in CI steps) otherwise the build will fail
52
52
53
-
The configuration service exposes all of its endpoints using Swagger.
53
+
The API exposes all of its endpoints using Swagger.
54
54
55
55
Swagger artefacts (docs.json/docs.yaml) are not stored within the repository as it is automatically generated using the [swag cli tool](https://github.com/swaggo/swag) and stored in the `docs/` directory. A helper function `make swag` can be run anytime to generate the most up to date swagger docs.
56
56
57
57
You can access the Swagger documentation to test and interact with the API at: [http://localhost:8080/swagger/index.html](http://localhost:8080/swagger/index.html)
58
58
59
59
## Configuration
60
60
61
-
You can configure configuration-service using environment variables or a `.env` file.
61
+
You can configure the API using environment variables or a `.env` file.
62
62
63
63
Available variables are shown in [`.env.example`](./.env.example)
64
64
@@ -69,14 +69,14 @@ cp .env.example .env
69
69
70
70
## Contributing
71
71
72
-
We welcome contributions to configuration-service!
72
+
We welcome contributions to the API!
73
73
74
74
## Testing
75
75
76
76
### Integration Tests
77
77
78
-
The Configuration Service contains integration tests, which will run tests against a real database, ensuring the service
79
-
works as expected.
78
+
The API contains integration tests, which will run tests against a real database, ensuring the service
79
+
works as expected.
80
80
81
81
The tests are marked with special build markers to avoid running them during normal development.
0 commit comments