Hi everyone, I'm new to the meltano game, and am ...
# infra-deployment
s
Hi everyone, I'm new to the meltano game, and am currently trying to create a CI/CD pipeline to automatically deploy our meltano project to our AWS environment. We currently do not have any framework to persist our states between build, and therefore have to re-sync everything at every build. Would anyone have suggestions on best practices to achieve this?
I read this blogpost https://meltano.com/blog/deploying-meltano-for-meltano/ which gave me some insights, but I'm new to terraform so I just want to confirm this is the way to go
v
The best practice is a production grade DB. So RDS Postgres, point meltano there. Another approach would be rds postgres serverless, another is to persist a local sql lite db between CI runs.
Terraform is an option, I'm not sure I'd introduce it in an environment just for Meltano but 🤷 to each their own!
s
@visch Awesome thank you so much! We may go the terraform route since my boss is pretty savy with it, but it's good to know we have options! And (this may sound dumb) but when we talk about keeping the current state, what do we want to keep? Like a copy of our .meltano folder?
v
This system database stores the state for you, this explains this in more depth!
s
Thank you so much! I'll keep you updated on how it goes 😄
Update: So currently I'm looking into setting up an EFS backend to store persisting data. We're currently running our meltano in ECS using docker.