You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should enable the ftl-provisioner in the dev environment, deployed with the ftl-cloudformation-plugin, and establish connectivity to that from ftl deploy to create databases in the dev environment
The text was updated successfully, but these errors were encountered:
Connects to the freshly created psql instance, and creates a database if
it does not exist.
This closes#3117 with
tbdeng/ftl-aws#35
We should refactor the DB creation from the success step to be part of
the actual provisioning flow. Thicket for this:
#3333
We should also not use the root credentials when connecting to the DB
from a module. However, we should change this when looking at DB
migrations, when we won't expect modules to execute DDL anymore.
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
We should enable the ftl-provisioner in the dev environment, deployed with the ftl-cloudformation-plugin, and establish connectivity to that from
ftl deploy
to create databases in the dev environmentThe text was updated successfully, but these errors were encountered: