Made the initiator.email optional and added a new validation.
Added a new regex pattern to string fields to prevent them from consisting only of whitespace.
Security-concept-update-needed: false
JIRA Work Item: [STACKITRMA-677](https://jira.schwarz/browse/STACKITRMA-677)
Adjust azure pr template to fit with the current jira board setup
Security-concept-update-needed: false.
JIRA Work Item: [STACKITRMA-553](https://jira.schwarz/browse/STACKITRMA-553)
The subject claim may contain underscore characters which are not allowed by the schema yet. Therefore, an adjustment of the regex in the schema has been made to allow it.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-437
Makes the request body accessible and modifiable in the audit event builder to enable SDK users to hide secrets in request bodies captured in the request body (by middlewares). Also updates dependencies.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-284
Allows the term "conway" as environment name in topic names.
Updates dependencies.
github.com/bufbuild/protovalidate-go@v0.9.3 requires go >= 1.23.4
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-249
Validates solace topic names to prevent issues when processing messages in the auditlog-appender.
Updates dependencies and build tools.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-220
Updates library versions to fix a reported vulnerability in a test dependency and to use latest versions.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-152
Updating the default connection pool size after clarifying with the Integration platform team.
Security-concept-update-needed: false.
JIRA Work Item: STACKITRMA-68
So far the SDK provided a messaging API that was not thread-safe (i.e. goroutine-safe). Additionally the SDK provided a MutexAPI which made it thread-safe at the cost of removed concurrency possibilities. The changes implemented in this commit replace both implementations with a thread-safe connection pool based solution.
The api gateway is a SDK user that requires reliable high performance send capabilities with a limit amount of amqp connections. These changes in the PR try address their requirements by moving the responsibility of connection management into the SDK. From this change other SDK users will benefit as well.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-62
* logging all errors related to the session and connection close
* closing the sender properly not only in case of an error
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-61
Updates library versions to fix a reported vulnerability in a test dependency and to use latest versions. Adds a convenience method to set the built flag in the builder without constructing an event.
Security-concept-update-needed: false.
JIRA Work Item: STACKITALO-40
Concurrent invocations on the SequenceNumberGenerator can lead to gaps and duplicate sequence numbers. To fix the issue an internal "backlog" is added as a buffer. If a new number is requested the "backlog" is checked first before creating a new number.
The "host" HTTP-Header is filtered out hide internal information.
The following build dependencies have been updated:
- Go has been updated to version 1.23.3.
- Golanglint-ci has been updated to version v1.62.0.
- Buf has been updated to version v1.46.0
The following library dependencies have been updated:
- go.opentelemetry.io/otel has been updated to version v1.32.0
- go.opentelemetry.io/otel/trace has been updated to version v1.32.0
Related work items: #696569
