see k8s_01#8

Description
currently slf4j is not in use, info should be provided about connections/new sessions etc

Use case or motivation behind the feature request
needed for traceability

Related issues

Additional context

Description

There are bunch of bad practices in tests so they should be cleaned up

Use case or motivation behind the feature request

Established unit tests procedure has all the details.
Short summary: Don't use try/catch or if/else statements in tests.

Related issues

Additional context

change default hostname to cfe-16, underscore is not allowed by the hostname specification.

Description

Replace getBytes("UTF-8") with getBytes(StandardCharsets.UTF_8)

Use case or motivation behind the feature request

It doesn't throw when using well defined StandardCharsets -> no need to do try/catch for something that we know is not going to throw

Related issues

Additional context

No: relpBatch.insert(syslogMessage.toRfc5424SyslogMessage().getBytes("UTF-8"));
Yes: relpBatch.insert(syslogMessage.toRfc5424SyslogMessage().getBytes(StandardCharsets.UTF_8));

          perhaps it would be proper to have somekind of "new client from ip" type of logging, based on guava cache that "if ip in cache, no log, expire cache in 300 seconds -> log expired, otherwise no log as it is a known client" same for a token.

Originally posted by @kortemik in #34 (comment)

Description
currently default is presented which may disclose information. use custom one.

Use case or motivation behind the feature request
custom one can be implemented to hide information: https://www.baeldung.com/spring-boot-custom-error-page

Related issues

Additional context

Describe the bug

JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk mvn clean package causes

repository/org/springframework/spring-context/6.1.2/spring-context-6.1.2.jar(org/springframework/stereotype/Component.class)
    class file has wrong version 61.0, should be 52.0
    Please remove or make sure it appears in the correct subdirectory of the classpath.

Expected behavior

Package is successful

How to reproduce

JAVA_HOME=/usr/lib/jvm/java-1.8.0-openjdk mvn clean package

Screenshots

Software version

At least commit 5376677

Desktop (please complete the following information if relevant):

• OS:
• Browser:
• Version:

Additional context

convert flaky tests to use relp, they are impacting CI.

create systemd service file for the rpm package

should be straight forward installable

      604  04-28-2023 05:43   BOOT-INF/classes/log4j2.xml
      263  04-28-2023 05:43   BOOT-INF/classes/application.properties.example
     4954  04-28-2023 05:43   BOOT-INF/classes/control.sh

jar currently contains these, however they should not be part of the build

   314932  12-04-2014 11:16   BOOT-INF/lib/junit-4.12.jar

final package should not contain test phase dependencies. please investigate the source for this

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project cfe_16: Failed to deploy artifacts: Could not transfer artifact com.teragrep:cfe_16:jar:1.0.3 from/to github (https://maven.pkg.github.com/teragrep/cfe_16): transfer failed for https://maven.pkg.github.com/teragrep/cfe_16/com/teragrep/cfe_16/1.0.3/cfe_16-1.0.3.jar, status: 409 Conflict -> [Help 1]

it is already present from previous stage

Description

Replace Cloudbees with rlo_14

Use case or motivation behind the feature request

rlo_14 is optimized for our use.

Related issues

Additional context

see cfe-32 for reference

Describe the bug
current configuration uses possibly default user, which is a privileged user.

Expected behavior
use non-privelged user for the container

How to reproduce
check which user is executing the service within the container

Screenshots

Software version

Desktop (please complete the following information if relevant):

• OS:
• Browser:
• Version:

Additional context
create a service user srv-cfe_16

Describe the bug
spring-boot-devtools are included

Expected behavior
spring-boot-devtools should not be included in the final product, use test if necessary to have them during tests.

How to reproduce
see https://github.com/teragrep/cfe_16/blob/1919b5f3f69d0c0f1b9256dc901cf5aba393e9b5/pom.xml#L91C1-L95C18

Screenshots

Software version

Desktop (please complete the following information if relevant):

• OS:
• Browser:
• Version:

Additional context

Tracking issue for:

• https://github.com/teragrep/cfe_16/security/code-scanning/1

Description

Current input format is arbitrary

Use case or motivation behind the feature request

Using arbitrary input format makes it hard to use established tools to do the heavy lifting for parsing and validating input data

Related issues

#26

Additional context