AnalyticsBucketDetails.constants.ts32 lines · main
| 1 | export const OPTION_ORDER = [ |
| 2 | 'catalog_uri', |
| 3 | 'vault_token', |
| 4 | 'warehouse', |
| 5 | 's3.endpoint', |
| 6 | 'vault_aws_access_key_id', |
| 7 | 'vault_aws_secret_access_key', |
| 8 | ] |
| 9 | |
| 10 | export const LABELS: Record<string, string> = { |
| 11 | vault_aws_access_key_id: 'S3 access key ID', |
| 12 | vault_aws_secret_access_key: 'S3 secret access key', |
| 13 | vault_token: 'Catalog token', |
| 14 | warehouse: 'Warehouse name', |
| 15 | 's3.endpoint': 'S3 endpoint', |
| 16 | catalog_uri: 'Catalog URI', |
| 17 | } |
| 18 | |
| 19 | export const DESCRIPTIONS: Record<string, string> = { |
| 20 | vault_aws_access_key_id: 'Matches the AWS access key ID from an S3 access key.', |
| 21 | vault_aws_secret_access_key: 'Matches the AWS secret access from an S3 access key.', |
| 22 | vault_token: 'Corresponds to the service role key.', |
| 23 | warehouse: 'Matches the name of this bucket.', |
| 24 | 's3.endpoint': '', |
| 25 | catalog_uri: '', |
| 26 | } |
| 27 | |
| 28 | // [Joshen] For context we've decided to decouple ETL from Analytics Buckets for now |
| 29 | // So this flag just hides all ETL-related user flows in Analytics Buckets |
| 30 | // Depending on future decision if we intend to keep it that way, then we might be able |
| 31 | // to clean up + deprecate the remaining ETL-related UI within Analytics Buckets |
| 32 | export const HIDE_REPLICATION_USER_FLOW = true |