Need to add uptime data

The function should return application uptime result.

Result example:
{ "componentType": "system", "observedValue": 1209600.245, "observedUnit": "s", "status": "pass", "time": "2018-01-17T03:36:48Z" }

Also need add unit tests

Need to add a connection check with ConsulKV

The function should take the ConsulKV connection options and return check the connection result.

Connection options example:
ConsulOptions: { let hostName: String let port: Int let requireHttps: Bool let requireBasicAuthentication : Bool let username: String? let password: String? }

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Also need add unit tests

Need to add a connection check with Kafka Producer

The function should take the Kafka Producer connection options and return check the connection result.

Connection options example:
brokers: "localhost:9092"

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Also need add unit tests

Need to add application health check

Result example:
{ "status": "pass", "version": "1", "releaseId": "1.2.2", "notes": [""], "output": "", "serviceId": "f03e522f-1f44-4062-9b55-9587f91c9c41", "description": "health of authz service", "checks": { }, "links": { "about": "http://api.example.com/about/authz", "http://api.x.io/rel/thresholds": "http://api.x.io/about/authz/thresholds" } }

Also need add unit tests

Problem

Currently, it is impossible to write unit tests for the PostgreDatabase functionality because it directly interacts with a running PostgreSQL server. This is inconvenient because it:

• Slows down development
• Requires a PostgreSQL server to be present
• Does not allow testing code in isolation

** Solution**
Make PostgreDatabase available as a Mock for writing unit tests. This will allow:

• Testing PostgreDatabase code in isolation
• Speeding up development
• Not depending on the presence of a PostgreSQL server

Describe alternatives you've considered

• Use a test PostgreSQL server. This is not very convenient because it requires its installation and configuration.
• Do not write tests for PostgreDatabase functionality. This is not recommended as it reduces the code quality.

Additional context
None

Need to add a connection check with Redis

The function should take the Redis connection options and return check the connection result.

Connection options example:
hostname: String, port: Int = RedisConnection.Configuration.defaultPort, password: String? = nil, tlsConfiguration: TLSConfiguration? = nil, database: Int? = nil, pool: [PoolOptions](https://api.vapor.codes/redis/documentation/redis/redisconfiguration/pooloptions) = .init()
or
serverAddresses: [SocketAddress], password: String? = nil, tlsConfiguration: TLSConfiguration? = nil, tlsHostname: String? = nil, database: Int? = nil, pool: [PoolOptions](https://api.vapor.codes/redis/documentation/redis/redisconfiguration/pooloptions) = .init()
or
url: URL, tlsConfiguration: TLSConfiguration? = nil, pool: [PoolOptions](https://api.vapor.codes/redis/documentation/redis/redisconfiguration/pooloptions) = .init()
or
url string: String, tlsConfiguration: TLSConfiguration? = nil, pool: [PoolOptions](https://api.vapor.codes/redis/documentation/redis/redisconfiguration/pooloptions) = .init()

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Need divides cases for data store and pub-sub mode

Also need add unit tests

Need to add a connection check with MongoDB

The function should take the MongoDB connection options and return check the connection result.

Connection options example:
connectionString: "<connection string>"

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Also need add unit tests

Need to add a connection check with PostgreSQL

The function should take the POSTGRESQL connection options and return check the connection result.

Connection options example:
hostname: "localhost", username: "username", password: "password", database: "database"
or
url: "<connection string>"

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Also need add unit tests

Need to add a connection check with Kafka Consumer

The function should take the Kafka Consumer connection options and return check the connection result.

Connection options example:
brokers: "localhost:9092"

Result example:
{ "componentId": "dfd6cf2b-1b6e-4412-a0b8-f6f7797a60d2", "componentType": "datastore", "observedValue": 75, "status": "warn", "time": "2018-01-17T03:36:48Z", "output": "", "links": { "self": "http://api.example.com/dbnode/dfd6cf2b/health" } }

Also need add unit tests

Describe the bug
GitHub Actions are failing to generate DocC documentation for the Library.

To Reproduce
Steps to reproduce the behavior:

1. Configure a GitHub workflow to use a DocC generation action (e.g., actions/checkout@v3, swift-tools/generate-documentation@latest).
2. Push your code changes to the repository.
3. Observe the workflow failing in the Actions tab of your repository.

Expected behavior
The workflow should successfully build your project, generate DocC documentation, and potentially deploy it to GitHub Pages.

Additional context

• This issue can manifest in various ways, including DocC generation errors, missing documentation artifacts, or deployment failures.
• Refer to the workflow logs for specific error messages.

Problem

Currently, it is impossible to write unit tests for the Redis Health Check functionality because it directly depends on a running Redis server. This is inconvenient because it:

• Slows down development
• Requires a Redis server to be present
• Does not allow testing code in isolation

Solution

Make Redis available as a Mock for writing unit tests. This will allow:

• Testing Redis Health Check code in isolation
• Speeding up development
• Not depending on the presence of a Redis server

Describe alternatives you've considered

• Use a test Redis server. This is not very convenient because it requires its installation and configuration.
• Do not write tests for Redis Health Check. This is not recommended as it reduces the code quality.

Additional context

None