Depends on #10 and #11 .
With event data being published to/flushed from S3, there is no need for fideslog to continue writing event data directly to the Snowflake DB. Any direct Snowflake DB interactions should be removed in favor of the S3-based mechanism.
To avoid duplicating event data in the Snowflake DB, any event data in the S3 bucket written before the deploy should be removed after deploying this change.
Depends on #10 and #11 .
With event data being published to/flushed from S3, there is no need for fideslog to continue writing event data directly to the Snowflake DB. Any direct Snowflake DB interactions should be removed in favor of the S3-based mechanism.
To avoid duplicating event data in the Snowflake DB, any event data in the S3 bucket written before the deploy should be removed after deploying this change.