Makefile updates (v0.12.3) #87
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
fix(containers): postgres
chore(containers): bump Conduit versiot to v0.12.3
kkopanidis
approved these changes
Mar 22, 2022
kkopanidis
pushed a commit
that referenced
this pull request
Mar 24, 2022
* feat(containers); database env vars fix(containers): postgres * fix(containers): master key env var not passed to Core * fix(containers): pass DB_PORT to mongodb and postgres * fix(containers): Makefile start-database * fix(containers): fix MongoDB chore(containers): bump Conduit versiot to v0.12.3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
-Bumped Conduit version from v0.12.2 to v0.12.3.
-Fixed PostgreSQL
-Overall improvements
Most notably, upgrading to v0.12.3 should greatly improve interaction with the Admin Swagger.
What kind of change does this PR introduce? (check at least one)
Container Makefile related changes, fixes and updates.
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
mainbranchfix #xxx, where "xxx" is the issue number)