Update from neicnordic/sensitive-data-archive at 06:41 on 2023-12-06

neicnordic · Dec 6, 2023 · 6f652af · 6f652af
1 parent 8f535ff
commit 6f652af
Show file tree

Hide file tree

Showing 6 changed files with 83 additions and 82 deletions.
diff --git a/docs/services/finalize.md b/docs/services/finalize.md
@@ -71,12 +71,12 @@ These settings control how `finalize` connects to the RabbitMQ message broker.
 - `DB_PASSWORD`: password for the database
 - `DB_DATABASE`: database name
 - `DB_SSLMODE`: The TLS encryption policy to use for database connections, valid options are:
-  - `disable`
-  - `allow`
-  - `prefer`
-  - `require`
-  - `verify-ca`
-  - `verify-full`
+    - `disable`
+    - `allow`
+    - `prefer`
+    - `require`
+    - `verify-ca`
+    - `verify-full`
 
   More information is available
   [in the postgresql documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION)
@@ -92,13 +92,13 @@ These settings control how `finalize` connects to the RabbitMQ message broker.
 
 - `LOG_FORMAT` can be set to `json` to get logs in JSON format. All other values result in text logging.
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`
 
 ### Storage settings
 

diff --git a/docs/services/ingest.md b/docs/services/ingest.md
@@ -86,12 +86,12 @@ These settings control how `ingest` connects to the RabbitMQ message broker.
 - `DB_PASSWORD`: password for the database
 - `DB_DATABASE`: database name
 - `DB_SSLMODE`: The TLS encryption policy to use for database connections, valid options are:
-  - `disable`
-  - `allow`
-  - `prefer`
-  - `require`
-  - `verify-ca`
-  - `verify-full`
+    - `disable`
+    - `allow`
+    - `prefer`
+    - `require`
+    - `verify-ca`
+    - `verify-full`
 
   More information is available
   [in the postgresql documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION)
@@ -113,16 +113,17 @@ The value of these variables define what other variables are read.
 The same variables are available for all storage types, differing by prefix (`ARCHIVE_`, or  `INBOX_`)
 
 if `*_TYPE` is `S3` then the following variables are available:
- - `*_URL`: URL to the S3 system
- - `*_ACCESSKEY`: The S3 access and secret key are used to authenticate to S3,
- [more info at AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
- - `*_SECRETKEY`: The S3 access and secret key are used to authenticate to S3,
- [more info at AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
- - `*_BUCKET`: The S3 bucket to use as the storage root
- - `*_PORT`: S3 connection port (default: `443`)
- - `*_REGION`: S3 region (default: `us-east-1`)
- - `*_CHUNKSIZE`: S3 chunk size for multipart uploads.
- - `*_CACERT`: Certificate Authority (CA) certificate for the storage system, this is only needed if the S3 server has a certificate signed by a private entity
+
+- `*_URL`: URL to the S3 system
+- `*_ACCESSKEY`: The S3 access and secret key are used to authenticate to S3,
+[more info at AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
+- `*_SECRETKEY`: The S3 access and secret key are used to authenticate to S3,
+[more info at AWS](https://docs.aws.amazon.com/general/latest/gr/aws-sec-cred-types.html#access-keys-and-secret-access-keys)
+- `*_BUCKET`: The S3 bucket to use as the storage root
+- `*_PORT`: S3 connection port (default: `443`)
+- `*_REGION`: S3 region (default: `us-east-1`)
+- `*_CHUNKSIZE`: S3 chunk size for multipart uploads.
+- `*_CACERT`: Certificate Authority (CA) certificate for the storage system, this is only needed if the S3 server has a certificate signed by a private entity
 
 and if `*_TYPE` is `POSIX`:
  - `*_LOCATION`: POSIX path to use as storage root
@@ -131,10 +132,10 @@ and if `*_TYPE` is `POSIX`:
 
 - `LOG_FORMAT` can be set to `json` to get logs in JSON format. All other values result in text logging.
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`
diff --git a/docs/services/intercept.md b/docs/services/intercept.md
@@ -53,10 +53,10 @@ These settings control how `intercept` connects to the RabbitMQ message broker.
 
 - `LOG_FORMAT` can be set to “json” to get logs in json format, all other values result in text logging.
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`
diff --git a/docs/services/mapper.md b/docs/services/mapper.md
@@ -65,12 +65,12 @@ These settings control how `mapper` connects to the RabbitMQ message broker.
 - `DB_PASSWORD`: password for the database
 - `DB_DATABASE`: database name
 - `DB_SSLMODE`: The TLS encryption policy to use for database connections, valid options are:
-  - `disable`
-  - `allow`
-  - `prefer`
-  - `require`
-  - `verify-ca`
-  - `verify-full`
+    - `disable`
+    - `allow`
+    - `prefer`
+    - `require`
+    - `verify-ca`
+    - `verify-full`
 
   More information is available in the [postgresql documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION)  
   Note that if `DB_SSLMODE` is set to anything but `disable`, then `DB_CACERT` needs to be set, and if set to `verify-full`, then `DB_CLIENTCERT`, and `DB_CLIENTKEY` must also be set.
@@ -109,10 +109,10 @@ and if `*_TYPE` is `POSIX`:
 
 - `LOG_FORMAT` can be set to `json` to get logs in JSON format. All other values result in text logging.
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`
diff --git a/docs/services/s3inbox.md b/docs/services/s3inbox.md
@@ -65,12 +65,12 @@ These settings control how verify connects to the RabbitMQ message broker.
 - `DB_PASSWORD`: password for the database
 - `DB_DATABASE`: database name
 - `DB_SSLMODE`: The TLS encryption policy to use for database connections, valid options are:
-  - `disable`
-  - `allow`
-  - `prefer`
-  - `require`
-  - `verify-ca`
-  - `verify-full`  
+    - `disable`
+    - `allow`
+    - `prefer`
+    - `require`
+    - `verify-ca`
+    - `verify-full`
 
   More information is available
   [in the postgresql documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION)  
@@ -99,10 +99,10 @@ These settings control how verify connects to the RabbitMQ message broker.
 
 - `LOG_FORMAT` can be set to “json” to get logs in json format. All other values result in text logging
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`
diff --git a/docs/services/verify.md b/docs/services/verify.md
@@ -88,12 +88,12 @@ These settings control how `verify` connects to the RabbitMQ message broker.
 - `DB_PASSWORD`: password for the database
 - `DB_DATABASE`: database name
 - `DB_SSLMODE`: The TLS encryption policy to use for database connections, valid options are:
-  - `disable`
-  - `allow`
-  - `prefer`
-  - `require`
-  - `verify-ca`
-  - `verify-full`
+    - `disable`
+    - `allow`
+    - `prefer`
+    - `require`
+    - `verify-ca`
+    - `verify-full`
 
   More information is available
   [in the postgresql documentation](https://www.postgresql.org/docs/current/libpq-ssl.html#LIBPQ-SSL-PROTECTION)
@@ -135,10 +135,10 @@ and if `*_TYPE` is `POSIX`:
 
 - `LOG_FORMAT` can be set to `json` to get logs in JSON format. All other values result in text logging.
 - `LOG_LEVEL` can be set to one of the following, in increasing order of severity:
-  - `trace`
-  - `debug`
-  - `info`
-  - `warn` (or `warning`)
-  - `error`
-  - `fatal`
-  - `panic`
+    - `trace`
+    - `debug`
+    - `info`
+    - `warn` (or `warning`)
+    - `error`
+    - `fatal`
+    - `panic`