Switch FeedStartOption to FeedVersion

[Weastie]

I believe that updating FeedStartOption to FeedVersion will mean that the adapter will always start off at the most recently collected data and continue forward. This way, if the Adapter is restarted or updated, and it missed 2 minutes of data, it should go back and collect the data from the point it stopped.

Please test this after implementation to make sure it doesn't collect too old of data (and fill up the DB unnecessarily)

Documentation: https://docs.google.com/document/d/1Y_9FnHPldeX4_aPViUUOi_8y2UJU1lKcfb1SBnu-lj8/edit?tab=t.0#heading=h.twpe67cpi1si

[github-actions]

Terraform plan output for ./terraform/common

Contains changes: no

Show Plan

data.aws_caller_identity.current: Reading...
data.aws_caller_identity.current: Read complete after 0s [id=880708401960]
aws_kms_key.common: Refreshing state... [id=489bf177-b6be-4403-852c-8fbb75f98d9b]
aws_kms_alias.common: Refreshing state... [id=alias/mygeotab-api-adapter]
aws_ssm_parameter.kms_arn: Refreshing state... [id=/mygeotab-api-adapter/common/kms_arn]
aws_ssm_parameter.kms_id: Refreshing state... [id=/mygeotab-api-adapter/common/kms_id]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Pusher: @Weastie

[github-actions]

Terraform plan output for ./terraform/env/prod

Contains changes: no

Show Plan

module.app.data.secretsmanager_login.rds_admin: Reading...
module.app.data.secretsmanager_field.rds_service_db: Reading...
module.app.data.secretsmanager_field.geotab_db: Reading...
module.app.data.secretsmanager_login.geotab: Reading...
module.app.data.secretsmanager_login.loki_basic: Reading...
module.app.data.secretsmanager_login.prometheus_basic: Reading...
module.app.data.secretsmanager_login.rds_service: Reading...
module.app.data.secretsmanager_login.prometheus_basic: Read complete after 0s [id=9edLxyQsbIoU5lw7K3m36w]
module.app.data.secretsmanager_field.geotab_db: Read complete after 0s [id=1YcOxbb1rBLJkhcf0nww4g/custom_field/database]
module.app.data.secretsmanager_login.rds_admin: Read complete after 0s [id=l3PcA08p731lSh6ht2SPWA]
module.app.data.secretsmanager_login.loki_basic: Read complete after 0s [id=TVNsnRso_U7J_raing91Dw]
module.app.data.secretsmanager_login.rds_service: Read complete after 0s [id=OIJwJeIvRv_lziXANk2TDw]
module.app.data.secretsmanager_field.rds_service_db: Read complete after 0s [id=OIJwJeIvRv_lziXANk2TDw/custom_field/database]
module.app.data.secretsmanager_login.geotab: Read complete after 0s [id=1YcOxbb1rBLJkhcf0nww4g]
module.app.aws_ssm_parameter.rds_service_db_name: Refreshing state... [id=/mygeotab-api-adapter/prod/rds_service_db_name]
module.app.aws_db_subnet_group.postgres: Refreshing state... [id=mygeotab-api-adapter-prod]
module.app.aws_ssm_parameter.geotab_db: Refreshing state... [id=/mygeotab-api-adapter/prod/geotab_db]
module.app.aws_ssm_parameter.enable_auto_start: Refreshing state... [id=/mygeotab-api-adapter/prod/enable_auto_start]
module.app.aws_iam_role.ec2: Refreshing state... [id=mygeotab-api-adapter-prod-ec2]
module.app.data.aws_ssm_parameter.kms_id: Reading...
module.app.aws_security_group.rds: Refreshing state... [id=sg-02a5621c258772d9c]
module.app.aws_security_group.ec2: Refreshing state... [id=sg-0fdcaae755d2fd30f]
module.app.aws_ssm_parameter.app_version: Refreshing state... [id=/mygeotab-api-adapter/prod/app_version]
module.app.data.aws_ssm_parameter.kms_arn: Reading...
module.app.data.aws_ssm_parameter.kms_arn: Read complete after 0s [id=/mygeotab-api-adapter/common/kms_arn]
module.app.aws_iam_policy.ssm: Refreshing state... [id=arn:aws:iam::880708401960:policy/mygeotab-api-adapter-prod-ssm]
module.app.data.aws_ssm_parameter.kms_id: Read complete after 0s [id=/mygeotab-api-adapter/common/kms_id]
module.app.aws_iam_policy.kms: Refreshing state... [id=arn:aws:iam::880708401960:policy/mygeotab-api-adapter-prod-kms]
module.app.aws_ssm_parameter.prometheus_user: Refreshing state... [id=/mygeotab-api-adapter/prod/prometheus_user]
module.app.aws_ssm_parameter.prometheus_pw: Refreshing state... [id=/mygeotab-api-adapter/prod/prometheus_pw]
module.app.aws_ssm_parameter.loki_pw: Refreshing state... [id=/mygeotab-api-adapter/prod/loki_pw]
module.app.aws_ssm_parameter.geotab_pw: Refreshing state... [id=/mygeotab-api-adapter/prod/geotab_pw]
module.app.aws_ssm_parameter.geotab_user: Refreshing state... [id=/mygeotab-api-adapter/prod/geotab_user]
module.app.aws_ssm_parameter.rds_service_user: Refreshing state... [id=/mygeotab-api-adapter/prod/rds_service_user]
module.app.aws_ssm_parameter.rds_service_pw: Refreshing state... [id=/mygeotab-api-adapter/prod/rds_service_pw]
module.app.aws_ssm_parameter.loki_user: Refreshing state... [id=/mygeotab-api-adapter/prod/loki_user]
module.app.aws_vpc_security_group_ingress_rule.rds_from_phl: Refreshing state... [id=sgr-0a0a75dd5c684b2dd]
module.app.aws_vpc_security_group_egress_rule.ec2_outbound_all_to_everywhere: Refreshing state... [id=sgr-04fec5b4fb0a7721c]
module.app.aws_vpc_security_group_ingress_rule.rds_from_app: Refreshing state... [id=sgr-0fbea7de4e9020990]
module.app.aws_vpc_security_group_ingress_rule.ec2_inbound_ssh_from_phl: Refreshing state... [id=sgr-0c4a90c67816aed1a]
module.app.aws_db_instance.postgres: Refreshing state... [id=db-PAGYZT7H5ZF7KKJJ4KO5JOI62E]
module.app.aws_iam_instance_profile.ec2: Refreshing state... [id=mygeotab-api-adapter-prod-ec2]
module.app.aws_iam_role_policy_attachments_exclusive.ec2: Refreshing state...
module.app.aws_ssm_parameter.rds_host: Refreshing state... [id=/mygeotab-api-adapter/prod/rds_host]
module.app.aws_launch_template.main: Refreshing state... [id=lt-01c28370c67b51cec]
module.app.aws_autoscaling_group.main: Refreshing state... [id=mygeotab-api-adapter-prod]

No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Pusher: @Weastie