fix!: change migration directory and migration flow, prune docker image #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🛑 BREAKING CHANGE
Existing old migration table
If you have a deployment of an old version of
als-consent-oracle
running you might need to drop your migration table due to previously depending on typescript migration files while now the migrations are dependent on their javascript compiled variants.Another potential option is to search the migration table and search for any .ts extension and update it to .js
Atm we haven't tested any solutions that don't result dropping the database since at this point in time the
als-consent-oracle
is not used in production anywhere.In an effort to lessen confusion when deploying, running migrations and configuring the service the docker image has been pruned to below