Last active
March 4, 2026 16:09
-
-
Save mkanoor/449f62ae6eb6ba55873c76b7adda3996 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| fields: | |
| - id: postgres_db_host | |
| type: string | |
| label: Postgres DB Host | |
| help_text: Postgres DB Server | |
| - id: postgres_db_port | |
| type: string | |
| label: Postgres DB Port | |
| default: '5432' | |
| help_text: Postgres DB Port | |
| - id: postgres_db_name | |
| type: string | |
| label: Postgres DB Name | |
| help_text: Postgres Database name | |
| - id: postgres_db_user | |
| type: string | |
| label: Postgres DB User | |
| help_text: Postgres Database user | |
| - id: postgres_db_password | |
| type: string | |
| label: Postgres DB Password | |
| secret: true | |
| help_text: Postgres Database password | |
| - id: postgres_sslmode | |
| type: string | |
| label: Postgres SSL Mode | |
| choices: | |
| - disable | |
| - allow | |
| - prefer | |
| - require | |
| - verify-ca | |
| - verify-full | |
| default: prefer | |
| help_text: Postgres SSL Mode | |
| - id: postgres_sslcert | |
| type: string | |
| label: Postgres SSL Certificate | |
| default: '' | |
| help_text: Postgres SSL Certificate | |
| multiline: true | |
| - id: postgres_sslkey | |
| type: string | |
| label: Postgres SSL Key | |
| secret: true | |
| default: '' | |
| help_text: Postgres SSL Key | |
| multiline: true | |
| - id: postgres_sslpassword | |
| type: string | |
| label: Postgres SSL Password | |
| secret: true | |
| default: '' | |
| help_text: Postgres SSL Password for key | |
| - id: postgres_sslrootcert | |
| type: string | |
| label: Postgres SSL Root Certificate | |
| default: '' | |
| help_text: Postgres SSL Root Certificate | |
| multiline: true | |
| - id: primary_encryption_secret | |
| type: string | |
| label: Primary Encryption Secret | |
| format: aes_key | |
| secret: true | |
| help_text: >- | |
| Used to derive AES keys for database encryption (note: may impact | |
| performance). Warning: This secret is not stored in our system; you must | |
| manually enter and remember it. If lost, an Activation reset is required. | |
| For key rotations, enter your new secret here and re-enter your previous | |
| secret into the Secondary Encryption Secret field to maintain access to | |
| historical events. | |
| - id: secondary_encryption_secret | |
| type: string | |
| label: Secondary Encryption Secret | |
| format: aes_key | |
| secret: true | |
| help_text: >- | |
| This field is used during key rotation to maintain access to legacy data. | |
| When updating your Primary Encryption Secret, you must manually re-enter | |
| your previous secret here. This allows the system to decrypt historical | |
| records while using the new string for future events. If left blank, the | |
| system assumes no rotation has occurred. | |
| - id: aes_salt | |
| type: string | |
| label: Salt | |
| format: aes_salt | |
| hidden: true | |
| secret: true | |
| help_text: >- | |
| To ensure cryptographic uniqueness, a random 32-byte salt is generated at | |
| the time of credential creation. This prevents identical input strings | |
| from producing the same AES key across different credentials. This field | |
| is managed automatically by the backend and remains hidden from the user | |
| interface. | |
| - id: expired_window_grace_period | |
| type: string | |
| label: Recovery Grace Period | |
| help_text: >- | |
| Specifies an additional time window in seconds to process events that expired | |
| while the system was offline. If the process restarts after a crash, this grace | |
| period is appended to the original window to allow for the ingestion of delayed | |
| data. If set to zero, events outside the original window will be dropped | |
| immediately upon restart. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment