Hey does anyone know if there is a way to find out...
# help
n
Hey does anyone know if there is a way to find out the master password which is created when the RDS instance is setup via sst? I am not sure if my migrations got applied correctly when they went to the dev stage as I can see a few errors in seed console, but not sure how to look at the actual db to prove that assumption
Ok so I figured out how to access credentials. For anyone looking in the future you can go to the secrets manager, there will be a secret there for your rds instance, grab the ARN and you can connect in via the query editor in rds dashboard 👌
I am still unsure about why my migrations didn't apply correctly and will continue to investigate unless anyone else has an idea 👍
I have been doing some digging and it seems like to run the migration scripts, you guys make a copy of the migration file in the directory
var/task/sst_rds_migration_scripts/
i did a bit of googling and it seems you can only create files in the
tmp/
directory of a lambda, and if you try to use another folder you might see the sort of error mentioned above. Wondering if you think this could be the cause of the issue at all @thdxr or @Frank Also curious if you guys have successfully ran migrations for an RDS instance on deploy before? It might just be me but not sure here. I did make sure my IAM role is setup properly too so I don't think it is a permissions error.
t
I think we fixed this in the latest sst
n
Seem to still get it, just updated sst to v0.69.0 and cloudwatch logs still giving me this 🤔
Also saw this in docs not sure if it is an old typo or if i need to configure something to enable running migrations?
Actually also unsure if unrelated but after update locally running sst yields this. Deploy seemed to work find though...
yea just to confirm I don't seem to be able to download the latest versions of sst since it breaks with the above message, could potentially be a windows thing but not 100% sure
f
Hey @Noah D I just fixed the issue above. It was a windows specific issue. Can you give the latest release a try v0.69.2?
Let me know if both the deploy issue and the migrations issue are fixed.
n
Hey frank, thanks for sorting those out, i will attempt to upgrade to most recent sst soon and let you know. For now had just applied the db migrations manually 😆 so hopefully it works
Hey @Frank so I have upgraded, i no longer get the issue mentioned before where i couldn't run sst, however the migrations did not get applied 🤔 I have tried manually deploying again as well as general code changes. Is there something I have to do to trigger the migrations?
I can also see the migration function and migration handler lambdas have not been run for a while as well
f
Hey @Noah D, sorry for the late follow up. Did you get migration to work?
If not, could you make a dummy change to one of your migration files (or add a new dummy migration), and trigger a deploy again?
If migration does not get run, DM me the link to the build on Seed, I will take a look.
n
Hey frank, sorry for taking a while to get back too! I just ran a dummy migration and seems like tables are applied as I would expect!
Thanks for the advice 🙏