Hinweis: Beginnend mit dem nächsten Release (GitLab 17.7) wird OpenSSL 3 verwendet. Alle TLS-Verbindungen erfordern TLS 1.2 oder höher. Schwächere Chiffren werden nicht mehr unterstützt. Die Verschlüsselung muss mindestens eine Sicherheit von 112 Bit aufweisen. // Starting with the next release (GitLab 17.7), OpenSSL 3 will be used. All TLS connections require TLS 1.2 or higher. Weaker ciphers are no longer supported. Encryption must have at least of 112 bits of security. https://docs.gitlab.com/ee/update/versions/gitlab_17_changes.html#1770
The implementation of #49 (closed) explicitly only handles variables of the FIRST struct encountered.
!52 (merged) can cause the entries to be reordered, in case of nested structs
The effort to handle multiple structs is not too big. So why not cover this, in case users' workflows organize the data in such a way?