From fe14a2c4f103b9d428556d9d7a01f30e086477b7 Mon Sep 17 00:00:00 2001 From: Randy Brookins Date: Wed, 6 Oct 2021 10:01:50 -0700 Subject: [PATCH 1/2] Update README.md --- README.md | 1 + 1 file changed, 1 insertion(+) diff --git a/README.md b/README.md index a1a5f5f5..c3500c6d 100644 --- a/README.md +++ b/README.md @@ -23,6 +23,7 @@ SQL recipes for Data Export analysis are in the [Data Export Cookbook](https://g 1. Download the latest [release binary](https://github.com/fullstorydev/hauser/releases) 2. Download the included `example-config.toml` file and customize it for your environment, including your FullStory API key, warehouse host, and credentials. AWS credentials (for S3) come from your local environment. + Your FullStory API key needs to have either the "Architect", or "Admin" permission level to create exports. 3. Assuming the binary and updated config are in the current directory, run: ```bash ./hauser -c myconfig.toml From c5f20cb5b5e212ebc02391ec5720c3defa4d6ec7 Mon Sep 17 00:00:00 2001 From: Randy Brookins Date: Wed, 6 Oct 2021 10:10:22 -0700 Subject: [PATCH 2/2] Update example-config.toml StartTime Update example-config.toml to require StartTime to not mislead those using the example. As of https://github.com/fullstorydev/hauser/pull/95/files StartTime is required or it returns an error such as Error: cannot parse "'2020-09-01T20:41:15Z'" as "". --- example-config.toml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/example-config.toml b/example-config.toml index b6acb83e..cbdacd60 100644 --- a/example-config.toml +++ b/example-config.toml @@ -22,9 +22,7 @@ ExportDuration = "6h" ExportDelay = "24h" # StartTime determines how far back to start exporting data if starting fresh. -# This should be an timestamp like with the followin format: 2018-12-27T18:30:00Z. -# If start time is empty, this will default to 30 days in the past. -StartTime = "" +StartTime = # Valid provider values: # * local: Used for downloading files to the local machine.